Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

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


Guidelines and tips
Guidelines and tips

Software Development Life Cycle, Study notes of Systems Engineering

SDLC stands for Software Development Life Cycle. It's a process used by software development teams to design, develop, test, and deploy high-quality software. The SDLC system encompasses a series of phases that guide the entire development process from inception to deployment and maintenance.The Software Development Life Cycle (SDLC) is a systematic process used by software development teams to design, develop, test, deploy, and maintain high-quality software products. It encompasses a series of phases that guide the entire software development process from inception to completion. These phases typically include planning, analysis, design, implementation, testing, deployment, and maintenance. The SDLC provides a structured approach to software development, ensuring that projects are completed efficiently, on time, and within budget, while meeting the needs and expectations of stakeholders.

Typology: Study notes

2022/2023

Uploaded on 04/13/2024

nguyen-huu-tri-fpi-hcm
nguyen-huu-tri-fpi-hcm 🇻🇳

4 documents

Partial preview of the text

Download Software Development Life Cycle and more Study notes Systems Engineering in PDF only on Docsity! ASSIGNMENT 2 BRIEF Qualification BTEC Level 4 HND Diploma in Computing Unit number Unit 7: Software Development Life Cycle Assignment title Undertake a Software Development Lifecycle Academic Year Unit Tutor Issue date Submission date IV name and date Submission Format: Format: ● The submission is in the form of 1 document. ● You must use the Times font with 12pt size, turn on page numbering; set line spacing to 1.3 and margins to be as follows: left = 1.25cm, right = 1cm, top = 1cm, bottom = 1cm. Citation and references must follow the Harvard referencing style. Submission: ● Students are compulsory to submit the assignment in due date and in a way requested by the Tutor. ● The form of submission will be a soft copy posted on http://cms.btec.edu.vn/. ● Remember to convert the word file into PDF file before the submission on CMS. Note: ● The individual Assignment must be your own work, and not copied by or from another student. ● If you use ideas, quotes or data (such as diagrams) from books, journals or other sources, you must reference your sources, using the Harvard style. ● Make sure that you understand and follow the guidelines to avoid plagiarism. Failure to comply this requirement will result in a failed assignment. Unit Learning Outcomes: Page 1 LO3 Undertake a software development lifecycle. LO4 Discuss the suitability of software behavioural design techniques. Assignment Brief and Guidance: Tasks At this stage, you have convinced Net Educational Institute (NEI) to select your project for development. Complete the following tasks to analyse and design the software. Task 1 – Analysis (1) 1. (P5) Undertake a software investigation to meet a business need. Undertake the software investigation to meet the business need using appropriate software analysis tools/techniques to carry out a software investigation and create a supporting documentation. You may submit this task in the form a report structured with background information, problem statements, data collection process and summary etc. In order to carry out the systems investigation you are required to identify the stakeholders, identify the requirements of the client, specify the scopes like inputs, outputs, processes and the process descriptors, consideration of alternative solutions and security considerations and the quality assurance applied. a) Identify the stakeholders, theirs roles and interests in the case study.  Introduction  Identify the stakeholders, theirs roles and interests  Requirement definition of the project ( FRs and NFRs)  List out FRs and NFRs in NEI project  Relationships between the FRs and NFRs b) Discuss the technique (s) you did use to obtain the requirements.  Introduction  Requirement gathering techniques  Conclusion. 2. (M3) Analyse how software requirements can be traced throughout the software lifecycle. Reference to your task above that required some level of intensive research work analyse how software requirements can be traced throughout the software lifecycle  Introduction to Requirements Management  Traceability  Traceability Matrix for NEI project Task 2 – Analysis (2) (P6) Analyze the requirements that you identified in Task 1 using a combination of structural and behavioral Page 2
Docsity logo



Copyright © 2024 Ladybird Srl - Via Leonardo da Vinci 16, 10126, Torino, Italy - VAT 10816460017 - All rights reserved