Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
SOFTWARE DEVELOPMENT LIFE CYCLE Assignment 2, Assignments for Network Design
Typology: Exams
1 / 13
This page cannot be seen from the preview
Don't miss anything!
Less flexible, limited adjustment range. It is difficult to measure development in each stage. The model is not suitable for long, ongoing projects, or complex projects, where there are many changes in requirements during the development life cycle. Difficult to return once a certain period has ended. B, Spiral model. 1,Description It is a model that combines the features of prototyping model and waterfall model. The spiral model is preferred for large, expensive and complex projects. This model uses the same stages as the waterfall model, in terms of ordering, planning, risk assessment, etc. Model analysis. The phases in the spiral development process include: Objective identification- Setting goals: defining objectives and objects for each phase of the project. Alternate evaluation- Risk assessment and mitigation: assess risk and take actions to reduce risk.
Product development- Product development: Selecting the right model for system development. Next phase planning- Planning: evaluate the project and plan for the next phase. 2, Advantages. Good for large-scale software systems. Easy to control the adventure at each level of evolution. Evaluation is more realistic as a workflow, because important problems are detected earlier. 3, Disadvantages. Managers need good skills to manage projects and assess risks in a timely manner. The cost is high and it takes a long time to complete the project. Complex and not suitable for small and low-risk projects. Frequent change requests lead to infinite iterations. Not widely used. C, Agile Model Agile is a flexible software development method to get products into the hands of users as quickly as possible and is seen as an improvement over older models such as the "waterfall" model or the "waterfall" model. "CMMI". Agile software development is a set of iterative and incremental development methodologies in which requirements and solutions are developed through collaborative alignment between autonomous and cross- functional teams.
Transfer of technology to new team members can be quite difficult due to lack of documentation. D, Iterative approach model. 1, Description. A model is iterated from start to full spec. The process is then repeated, creating a new version of the software at the end of each iteration of the model. Instead of developing software from the specification and then starting to execute, this model can be reviewed gradually to arrive at the final requirements. 2, Restrictions. Demand for many resources. System architecture or design problems can arise at any time. Management requirements are more complex. The progress of the project is highly dependent on the risk analysis phase. E, Growth Model.
1, Description. Spec is divided into several parts. The cycle is divided into small, easy-to-manage modules. Each module will go through the requirements for design, implementation, etc. like a normal development life cycle. 2, Advantages. Rapid development. This model is more flexible, less expensive when scope and requirements change. Easier to check and correct. 3, Disadvantages. Need good planning and design. Total cost is higher than waterfall model. F,V model(V model).
1, Description. Break requirements down into phases. Each phase (sprint) only makes a certain number of requests. Each sprint usually lasts from 1 week to 4 weeks (no longer than 1 month). At the beginning of the sprint, what requirements will be planned. After that, will execute the code and test. At the end of the sprint is a finished product both code and test that can be demoed and run. Complete sprint 1, continue to do sprint 2, sprint... until all requirements are completed. In each sprint, there will be a daily meeting - a daily meeting of 15-20 minutes. Each member will report: What did I do yesterday? What will I do today? Have any difficulties? Scrum is a customer-oriented model. 2, Advantages. One person can do many things for example dev can test. Detect errors early. Capable of being applied to projects where customer requirements are not clear at the outset. 3, Disadvantages. The level of the group requires a certain skill. Must have an understanding of the aglie model. Difficulty determining budget and timing. Always listen to feedback from customers and change accordingly, so it will take a long time. The role of the PO is very important, the PO is the product oriented person. If the PO does not do well, it will affect the overall result. H, RAD Model.
1, Description. RAD modeling is a software development methodology that uses minimal planning in favor of rapid prototyping. Functional modules are developed in parallel as prototypes and integrated to create the finished product for faster product delivery. Ensure that the developed prototypes are reusable. 2, Advantages. Reduce development time. Increase the reusability of components. Make a quick initial assessment. Encourage customers to give feedback. 3,Disadvantage The level of the group requires a certain skill. Only systems with modules can use this model. LO2: Explain the importance of a possible study A, Feasibility study A feasibility study is an assessment of the practicality of a project or system. A study aims to objectively and rationally uncover the strengths and weaknesses of an existing business or proposed venture, opportunities and threats present in the natural environment, the resources required to carry through, and ultimately the prospects for success. B, Evaluation criteria for feasibility study. Technical feasibility: this assessment focuses on the technically available resources within the organization. It helps the organization determine if the technical resources are suitable for capacity and whether the technical team is capable of applying new ideas to the system. Technical feasibility also involves an assessment of hardware, software, and other technical needs. In an exaggerated way, a business wouldn't install a massive Star Trek-like transportation system into its factory, because then the project wouldn't be technically viable.
