SDLC
2019
Puran Bohara (HND/ second semester)
1
ASSIGNMENT COVER SHEET
STUDENT DETAILS
Student ID
Family Name
Reg No.
Bohara
Given Name
Puran
Enrolment Year
2018
Section
P2
Semester
2nd
Email
UNIT DETAILS
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
Guidelines and tips
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
SDLC Assignment: Tracing Requirements & Model Comparison, Study Guides, Projects, Research of Computer Science
An assignment cover sheet for a student named Puran Bohara in the HND second semester. The assignment requires analyzing how software requirements can be traced throughout the software lifecycle and differentiating between finite state machines (FSM) and extended finite state machines (EFSM). The document also includes justifications for data-driven software and explanations of how user and software requirements have been addressed.
Typology: Study Guides, Projects, Research
2019/2020
1 / 51
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download SDLC Assignment: Tracing Requirements & Model Comparison and more Study Guides, Projects, Research Computer Science in PDF only on Docsity!
ASSIGNMENT COVER SHEET
STUDENT DETAILS
Student ID Family Name Reg No. Bohara Given Name Puran Enrolment Year 2018 Section P Semester (^) 2nd Email [email protected]
UNIT DETAILS
Unit Title SDLC Unit Code J/615/ Assessor Name Shiva poudel^ Issued Date 10 Aug 2019 Assignment Title College Management System Development Lifecycle Assignment No (^) 01 Submission Date 26 Jun, 2021 Qualification BTECH HND Campus ISMT
STUDENT ASSESSMENT SUBMISSION AND
DECLARATION
When submitting evidence for assessment, each student must sign a declaration confirming that the work is their own. Student Name Puran Bohara Assessor Name Shiva poudel Issue Date (^) 10 Aug 2019 Submission Date 26 Jun 2021 Programme BTECH HND Unit Name (^) SDLC
BTEC HND in Computing Unit 9: Software Development Lifecycle Unit Code : J/615/ Session/Year: 2018/19 Assessment No: 01 Assignment Launch Date : 10 Aug 2019 Due Date : Sept 30, 2019 Assignment Title : College Management System Development Lifecycle Teacher Name: Shiva Poudel (^) Iv’s Name & Date : Student Name: Pearson Reg No: Final Grade: Assignment submission format Each student has to submit their assignment as guided in the assignment brief. The students are guided what sort of information is to produce to meet the criteria targeted. Some tasks might require group work, but the student has to produce individual assignment. Scenario I New Republica College which is predominantly operating in Nepal is offering an education to many nationals and international students. You work as a systems analyst for a New Republica college which is developing the new college management system. This system will handle college accounting system, library management and assignment tracking system. The college has a small systems development team which in the past has been solely responsible for all development work. The Principal of the College feels that the development team has not been outward looking and wants a fresh approach for the new system. The in-house team will work alongside analysts and developers from your team who will lead the project.
You will be project managing the analysis and design stage of the new system. Your first task is to update the in-house team on the developments in new methodologies used to analyze systems. Most of the in-house team uses only the more traditional approaches and few are fully aware of the agile methodologies which are growing in popularity. Part: 1 As a part of your responsibility you are required to prepare a report that describes different software development cycles. Your report must include the following:
- Description of predictive and adaptive software development models considering at least two iterative and two sequential models.
- The risks involved in each of the models and how the risk can be mitigated /managed in each model by taking a reference of the spiral model. Once you have prepared the report you are required to produce documentation that
- Describe with an example why a particular lifecycle model is selected for a development environment. You may consider a different development environment with different business logics, platform, etc., and the applicability of the particular software development model over the development environment.
- Assess the merits of applying the waterfall model to a large software development project with appropriate evidenced researched work with reference to the current context. Part: 2
- You are required to produce a documentation that explains the purpose of the feasibility report and describe how technical solutions can be compared.
- Prepare a brief report discussing the components of the feasibility report.
- Carry out the feasibility study as per the best of your previous research work against the solution to be developed for the given problem and assess the impact of different feasibility criteria on the software investigation. Part: 3
- Undertake the software investigation to meet the business need using appropriate software
an application for both.
- Present justifications of how data driven software can improve the reliability and effectiveness of the software. Pass Merit Distinction LO1: Describe different software development lifecycles D1 Assess the merits of applying the waterfall lifecycle model to a large software development P1 Describe two iterative and two sequential lifecycle models. M1 Describe, with an example, why a particular lifecycle model is selected for a development P2 Explain how risk is managed in the spiral lifecycle model. environment. project. LO2: Explain the importance of a feasibility study. D2 Assess the impact of different feasibility criteria on software investigation. P3 Explain the purpose of a feasibility report. P4 Describe how technical solutions can be compared. M2 Discuss the components of feasibility report. LO3: Undertake a software development lifecycle. D3 Critically evaluate how the use of the function design paradigm in the software development lifecycle can improve the software quality. P5 Undertake a software investigation to meet a business need. P6 Use appropriate software analysis tools/techniques to carry out a software investigation and create supporting documentation. M3 Analyze how software requirements can be traced throughout the software lifecycle. M4 Discuss two approaches to improving software quality LO4: Discuss the suitability of software behavioral design techniques D4 Present justifications of how data driven software can improve
P7 Explain how user and software requirements have been addressed. M5 Suggest two software behavioral specification methods and illustrate their use with an example. M6 Differentiate between a finite state machines (FSM) and an extended FSM, providing an application for both. the reliability and effectiveness of the software. To be used by the assessor. General feedback on the assignment : In order to pass the unit the learner has to meet all the pass criteria. Tick the each criteria awarded. P1 P2 P3 P4 P5 P6 P7 Pass Achieved / Not In order to be awarded a Merit the learner has to meet all the pass criteria and all the merit criteria. Tick the criteria awarded. M1 M2 M3 M4 M5 M6 Merit achieved / Not In order to be awarded a Distinction the learner has to meet all the pass merit criteria and all the Distinction criteria. Tick the criteria awarded.
Assignment Prepared By: Shiva Poudel Signature: Date: 10 Aug 2019 Brief Checked By: Dhruba Babu Joshi Signature: Date: 10 Aug 2019
Submitted By: Full Name: Puran Bohara Course: BTEC HND Semester: Second Section: D Year of enrollment: 2018 Submitted To: Teacher Name: Shiva Poudel Subject: SDLC
Introduction: In this part, I have described about the different methods of software development cycles. Software Development Life Cycle Process: "Software development life cycle is the procedure followed for a product venture, inside a product association" (techtarget, n.d.). SDLC is the arrangement of steps used to deal with the periods of advancement for a data system. SDLC comprises of a neat and clean arrangement depicting how to create, keep up, supplant and adjust or improve explicit programming. The existence cycle characterizes the philosophy for improving the nature of programming and the general advancement process. It is common methodology for system development in all approaches. It consists of six phases which are listed below: Requirement Analysis Defining the project Designing Coding Testing Deployment Maintenance
Fig: SDLC process Types of software developing life cycle (SDLC): Waterfall Model V-shaped model Evolutionary Prototyping Model Spiral Model Iterative and incremental method Agile development method Iterative Model: Definition: The Iterative model is a specific execution of programming advancement life cycle (SDLC) that centers around an underlying, disentangled usage, which at that point dynamically gains intricacy and a more extensive list of capabilities until the last framework is finished. Iterative and steady
where the project is at where it needs to be what can or should change, and so on. These are the most important stages of iterative models. There are mainly two types of iterative model which are described below: Prototyping model: “The prototyping model is a systems development method in which a prototype is built, tested and then reworked as necessary until an acceptable outcome is achieved from which complete system or product can be developed” (techopedia, n.d.). The prototyping model is one of the most famously utilized programming advancement lifecycle models SDLC models. This model is utilized when the clients don't have the foggiest idea about the specific venture prerequisites in advance. Right now, model of the finished result is first evolved, tried and refined according to client input over and again until a last worthy model is accomplished which shapes the reason for building up the last item. Fig: prototype model Steps in prototype model:
1. Requirements gathering and analysis: A prototyping model .starts with requirement. analysis. In this phase the requirements of .the system are defined in detail. During this process, the users of the system are interviewed to know what their .expectation from the system is. 2. Quick design: The second phase is a preliminary design or a quick design. In this stage, a simple design of the system is created. However, it is not a complete design. It gives a brief idea of the system
to the user. The quick design helps .in developing the prototype.
3. Build a prototype: In this phase, an .actual prototype is designed based on the information gathered from quick design. It is a short working model of the necessary system. 4. Initial user evaluation: In this stage, the proposed system is presented to the client for an initial evaluation. It helps to find out the strength and .weakness of the working model. Comment and .suggestion are collected from the .customer and provided to the .developer. 5. Refining prototype: If the user is not satisfied with the provided prototype, we need to refine the prototype according to the user’s feedback and suggestion. 6. Implementation product and maintenance: Once the eventual system is developed based on the final prototype, it is thoroughly tested and deployed to the .production members. The system undergoes routine maintenance for minimizing downtime .and prevent large scale failures. Advantages of prototype model: Users are actively involved in the development. Errors can be detected easily and much earlier. Quicker user .feedback is available .leading to better .solutions. Flexibility in .design. New requirements .can be easily accommodated .as there is scope for .refinement. Disadvantages of prototype model: Costly with respect .to time and .money. Leads to implementing .and then repairing .way of building systems. It is very difficult for the developers to accommodate all the changes demand by the customers. Developers in a hurry to build prototypes may end. The customers might lose interest in the product if he/she is not satisfied with the initial prototype. Agile methodology: Agile programming advancement contains different ways to deal with programming improvement