Fundamental process activities 1. Software specification 2. Software development 3. Software validation 4. Software evolution 1. Software specification Documenting the expectation on the system to be built. 2. Software development Designing and implementation 3. Software validation Checking ana verifying the system 4. Software evolution Needs to be changed and upgraded with time SDLC SDLC stands for software development life cycle and it includes, 1. Planning 2. Defining 3. Designing 4. Building 5. Testing 6. Deployment SDLC is helps developers create high quality software products. Q1: Explain 5 different software life cycle modules Life cycle models in SDLC 1. Waterfall A linear-sequential model where each phase must be completed before the next begins. • • • • Simple and easy to understand Clear milestones and deliverables Well suited for small projects Documentation emphasis Feasibility study • • • • Technical feasibility Economic feasibility Schedule feasibility Operational feasibility Requirement gathering • • Pay attention to how staff and patrons interact with existing systems and processes. Use surveys to gather feedback from a wider audience, including library users. SRS: The SRS forms the basis of a legal contract with the customer. DSD: Decisions are made about hardware, software and the system architecture. Development: A set of developers code the software as per the established design specifications, using a chosen programming language Testing: The testing phase ensures that the software requirement are in lace and that the software works as expected. 2. Spiral Combines the properties of the prototyping model and the waterfall model, and is good for large projects • • • • Risk management Flexibility and iterative development Customer involvement Adaptability to change 3. Incremental Software is developed in small, iterative cycles, where each cycle builds upon the previous one • • • • • Early delivery of functionality Reduced risk Feedback incorporation Flexibility and adaptability Improved quality 4. Prototyping A prototype is built, tested, and reworked if necessary, and works best when there are known project requirements in detail ahead of time • • • • Early feedback and validation Improved requirement understanding Early detection of issues Reduces development time 5. V-model Also known as the Verification and Validation model, this model has processes that are executed sequentially in a V-shape. It is based on the association of a testing phase for each development stage. • • • • Clarity and structure Early focus on testing Traceability Risk management 6. Agile model An interactive, iterative, and team-based approach to development that focuses on constant, concise production. Agile is the most popular method in SDLC, as it ensures good interactions between all members of the development lifecycle. • • • • Flexibility and adaptability Customer satisfaction Early and continuous delivery Transparency and visibility 7. DevOps model A newer model that involves the development and operation teams of an organization. The goal is to streamline product delivery and support while minimizing organizational risks. • • • • Faster delivery Improved collaboration Increased efficiency Enhanced quality Q2: What are the feasibility criteria for a ‘Library System’? 1. Technical feasibility, • • Can the current technology handle the library system's requirements? Do we have the expertise to develop and maintain the system? 2. Economic feasibility, • • Is there a positive return on investment? Can we afford the initial investment and ongoing maintenance costs? 3. Operational feasibility • • Will staff and patrons accept and adapt to the new system? Are there sufficient resources for training and support? 4. Schedule feasibility • • Can the project be completed within the proposed timeline? Are there clear milestones and deliverables?
