Prepare for your exams
Get points
Guidelines and tips
Sell on Docsity
Docsity AI

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

Sell on Docsity

Docsity AI

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents

20 Points

For each uploaded document

Answer questions

5 Points

For each given answer (max 1 per day)

All the ways to get free points

Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

Software Development Life Cycle (SDLC): Stages, Need, and Requirements Traceability, Lecture notes of Software Development

Tribhuvan University Kathmandu Software Development

Lecture Hand notes of Software Development Lifecycle

Typology: Lecture notes

2020/2021

Uploaded on 06/04/2021

pkhokhali 🇳🇵

(1)

18 documents

1 / 16

This page cannot be seen from the preview

Don't miss anything!

SDLC stages

•A software life cycle model (also termed

process model) is a pictorial and diagrammatic

representation of the software life cycle.

•A life cycle model represents all the methods

required to make a software product transit

through its life cycle stages.

•It also captures the structure in which these

methods are to be undertaken.

Discover Lecture notes of Software Development Tribhuvan University Kathmandu

Partial preview of the text

Download Software Development Life Cycle (SDLC): Stages, Need, and Requirements Traceability and more Lecture notes Software Development in PDF only on Docsity!

SDLC stages

(^) A software life cycle model (also termed process model) is a pictorial and diagrammatic representation of the software life cycle.
(^) A life cycle model represents all the methods required to make a software product transit through its life cycle stages.
(^) It also captures the structure in which these methods are to be undertaken.

Need of SDLC

(^) Without using an exact life cycle model, the development of a software product would not be in a systematic and disciplined manner.
(^) When a team is developing a software product, there must be a clear understanding among team representative about when and what to do.

SDLC Cycle

(^) SDLC Cycle represents the process of developing software. SDLC framework includes the following steps:

Planning and requirement analysis

(^) Requirement Analysis is the most important and necessary stage in SDLC.
(^) The senior members of the team perform it with inputs from all the stakeholders and domain experts or SMEs in the industry.
(^) Planning for the quality assurance requirements and identifications of the risks associated with the projects is also done at this stage.

Feasibility study

(^) It is defined as the practical extent to which a project can be performed successfully.
(^) It determines whether the solution considered to accomplish the requirements is practical and workable in the software.
(^) Information such as resource availability, cost estimation for software development, benefits of the software to the organization after it is developed and cost to be incurred on its maintenance are considered during the feasibility study.

Defining Requirements

(^) Once the requirement analysis is done, the next stage is to certainly represent and document the software requirements and get them accepted from the project stakeholders.
(^) This is accomplished through "SRS"- Software Requirement Specification document which contains all the product requirements to be constructed and developed during the project life cycle.

Developing the project

(^) In this phase of SDLC, the actual development begins, and the programming is built. The implementation of design begins concerning writing code. Developers have to follow the coding guidelines described by their management and programming tools like compilers, interpreters, debuggers, etc. are used to develop and implement the code.

Testing the project

(^) After the code is generated, it is tested against the requirements to make sure that the products are solving the needs addressed and gathered during the requirements stage.
(^) During this stage, unit testing, integration testing, system testing, acceptance testing are done.

Maintenance

(^) Once when the client starts using the developed systems, then the real issues come up and requirements to be solved from time to time.
(^) This procedure where the care is taken for the developed product is known as maintenance.

Requirements traceability

(^) Requirements traceability ensures that each business need is tied to an actual requirement, and that each requirement is tied to a deliverable.
(^) It refers to the capability of a requirements management process or tool which enables the process participant or tool to follow the life of a requirement both forwards and backwards.
(^) It also refers the ability to link requirements (via specific relationships) to other constructs or artifacts of the product development lifecycle.

Why Requirements traceability?

Tracing requirements, when done properly, saves time, money, and effort on the part of the analyst, the project sponsors and the parent organization.

(^) It ensures that final deliverables directly tie to initial business needs.
(^) it ensures that organizations do not waste time and resources repeating research.
(^) It offers much easier impact analysis.