Download Software Development Life Cycle Assignment 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:
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)
- (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_._
- (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
Software behavioural design techniques, such as FSM and ESML, help define system behaviour. FSM are mathematical models with finite states, like a light switch, while ESML allows for more complexity. Behavioural tools, like Sequence and Use Case Diagrams, visualise interactions and functionality, respectively. There are also various software behavioural tools, like Sequence Diagrams and Use Case Diagrams. A sequence diagram visualises interactions between different parts of a system, for example, the communication sequence in a login operation. Draw a Sequence Diagram showing operations: adding, editing, deleting user information of the NEI system
- (M6) Differentiate between a finite state machine (FSM) and an extended FSM, providing an application for both. Finite State Machine (FMS) Extended Finite State Machine Diference Between Finite And Extended Finite State Machine
- (D4) Discuss how the data-driven approach improves the reliability and effectiveness of software.
Definition Of Data Driven Sofware Data Driven Sofware For Improvement Of Reliability And Efectiveness Of The Sofware Improving The Dependability And Efectiveness Of The Sofware Using Data Driven Sofware
Learning Outcomes and Assessment Criteria
Pass Merit Distinction
LO3 Undertake a software development lifecycle
D3 Evaluate the process of undertaking a systems investigation with regard to its effectiveness in improving a 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 Analyse how software requirements can be traced throughout the software lifecycle.
M4 Discuss two approaches to improving software quality.
LO4 Discuss the suitability of software behavioural design techniques
D4 Present justifications of how data driven software can improve the reliability and effectiveness of software.
P7 Discuss, using examples, the suitability of software behavioural design techniques.
M5 Analyse a range of software behavioural tools and techniques.
M6 Differentiate between a finite state machine (FSM) and an extended FSM, providing an application for both.
