Assignment 1 _ Software Life Cycle, Study Guides, Projects, Research of Computer Science

Download Assignment 1 _ Software Life Cycle and more Study Guides, Projects, Research Computer Science in PDF only on Docsity!

Higher Nationals in Computing

Unit 9: Software Development Life Cycle

ASSIGNMENT 1

Assessor name: PHAN MINH TAM

Learner’s name: Nguyen Huy Nhat Tan

ID: GCS

Class: GCS1004A

Subject code: 1631

Assignment due: Assignment submitted:

❒ Summative Feedback: ❒ Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

Assignment Brief 01 (RQF)

Higher National Certificate/Diploma in Business

Student Name/ID Number: GCS210161 Nguyen Huy Nhat Tan Unit Number and Title: Unit 09: Software Development Life Cycle Academic Year: 2021 – 2022 Unit Assessor: TamPM Assignment Title: Plan a software development life cycle Issue Date: 10/Jan/ Submission Date: Internal Verifier Name: 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.greenwich.edu.vn/. ● Remember to convert the word file into PDF file before the submission on CMS.

● Purchase individual downloads at a fixed fee per download. ● Establish a customer subscription account permitting unlimited downloads for a monthly fee. ● Purchase music download gift cards. Business Value: We expect that Tune Source will increase sales by enabling existing customers to purchase specific digital music tracks and by reaching new customers who are interested in our unique archive of rare and hard-to-find music. We expect to gain a new revenue stream from customer subscriptions to our download services. We expect some increase in cross-selling, as customers who have downloaded a track or two of a CD decide to purchase the entire CD in a store or through our website. We also expect a new revenue stream from the sale of music download gift cards. Conservative estimates of tangible value to the company include the following: ● $757,500 in sales from individual music downloads. ● $950,000 in sales from customer subscriptions. ● $205,000 in additional in-store or website CD sales. ● $153,000 in sales from music download gift cards. Special Issues or Constraints: ● The marketing department views this as a strategic system. The ability to offer digital music downloads is critical in order to remain competitive in our market niche. Our music archive of rare and hard-to- find music is an asset that is currently underutilized. ● Many of our current loyal customers have been requesting this capability, and we need to provide this service or face the loss of these customers’ business. ● Because customers have a number of music download options available to them elsewhere, we need to bring this system to the market as soon as possible. Tasks Complete the following tasks: Task 1 – SDLC model You are a project manager of a company named ABC. Your company has been hired by Tune Source to carry out a project that helps them develop a software for the requirements specified in the system request. As the first step, you need to:

1. Describe the following SDLC models: waterfall, v-model, prototyping, scrum and spiral. Choose one that

you think suitable for the project and explain why. ● 350 - 500 words for each model. ● Explanation: 400 – 600 words. Discuss the suitability of each of the SDLC models for the project. For each model, specify whether it is most, moderately or least suitable. ● Word limit: 800 - 1000 words. Discuss the merits of applying the waterfall model to a large software development project. ● Word limit: 800 – 1200 words.

2. Identify some risks and discuss an approach to manage them. You will have the present what is Risk Management process with clear illustrations and explanations. Then you will create a Risk Management Matrix to assess and manage risks of Tune Source project. ● Word limit: 600 – 1000 words. Task 2 – Feasibility study
3. Discuss the purpose of conducting a feasibility study for the project. ● Word limit: 400 – 600 words.
4. Discuss how the three feasibility criteria (technical, economic, organizational) are applied to the project. Discuss whether the project is feasible. Discuss alternative technical solutions using the alternative matrix. ● Word limit: 1200 – 1500 words.
5. Explain the components of a feasibility report. Discussion economic feasibility study on Tune Source project (NPV, Cashflow, Break-Even Point) ● Word limit 350 – 500 words. Discussion organizational feasibility study on Tune Source project ● Word limit 350 – 500 words.

Learning Outcomes and Assessment Criteria (Assignment 01): Learning Outcome Pass Merit Distinction LO1 Describe different software development lifecycles P1 Describe two iterative and two sequential software lifecycle models. P2 Explain how risk is managed in the Spiral lifecycle model. M1 Describe, with an example, why a particular lifecycle model is selected for a development environment. D1 Assess the merits of applying the Waterfall lifecycle model to a large software development project. LO2 Explain the importance of a feasibility study P3 Explain the purpose of a feasibility report. P4 Describe how technical solutions can be compared. M2 Discuss the components of a feasibility report. D2 Assess the impact of different feasibility criteria on a software investigation.

Contents

A method for iterative software development called the spiral model concentrates on risk management. The

• Unit 9: Software Development Life Cycle ASSIGNMENT 1.......................................................................................
  • Assignment Brief 01 (RQF)......................................................................................................................................
    • Higher National Certificate/Diploma in Business.................................................................................................
• A. Describe two iterative and two sequential software life cycle models (P1)........................................................
• 1. Introduction to System development lifecycle....................................................................................................
     • 1.1. Definition of System Development Life Cycle (SDLC)....................................................................................
     • 1.2. Purposes of SDLC..........................................................................................................................................
• 2. Two sequential software lifecycle models...........................................................................................................
     • 2.1. Waterfall model............................................................................................................................................
     • 2.1.1. Definition..................................................................................................................................................
     • 2.1.2. Advantages...............................................................................................................................................
     • 2.1.3. Disadvantages...........................................................................................................................................
     • 2.1.4. When to use.............................................................................................................................................
     • 2.2. Reuses – Oriented Software Engineering......................................................................................................
     • 2.2.1. Definition..................................................................................................................................................
     • 2.2.2. Advantages...............................................................................................................................................
     • 2.2.3. Disadvantages...........................................................................................................................................
     • 2.2.4. When to use.............................................................................................................................................
• 3. Two iterative software lifecycle models..............................................................................................................
     • 3.1. Incremental Development............................................................................................................................
     • 3.1.1. Definition..................................................................................................................................................
     • 3.1.2. Advantages...............................................................................................................................................
     • 3.1.3. Disadvantages...........................................................................................................................................
     • 3.1.4. When to use.............................................................................................................................................
     • 3.2. Spiral model..................................................................................................................................................
• 4. The model is used in the Tune Source project.....................................................................................................
• primarily a retailer................................................................................................................................................... Spiral Model may still be applied to improve Tune Source's website production process even if the firm is
• The Spiral Model might be used in the creation of the Tune Source website:........................................................
• • Establish goals and specifications.........................................................................................................................
• • Recognize and assess potential dangers...............................................................................................................
• • Create a website prototype..................................................................................................................................
• • Test and assess the prototype..............................................................................................................................
• • Improve the prototype depending on input.........................................................................................................
• • Launch the website...............................................................................................................................................
• • Track and modify the website throughout time...................................................................................................
• B. Explain how risk is managed in the Spiral lifecycle model (P2)............................................................................
• 1. Risk management................................................................................................................................................
• 2. Risk management process...................................................................................................................................
• 3. Risk management matrix in Tune Source project..............................................................................................
• 4. How to manage risks in the Spiral lifecycle model.............................................................................................
• C. Explain the purpose of a feasibility report (P3).................................................................................................
• 1. What is a feasibility study..................................................................................................................................
• 2. The purpose of a feasibility report....................................................................................................................
• 3. Feasibility study on Tune Source project...........................................................................................................
  • 3.1. Economic feasibility....................................................................................................................................
  • 3.2. Organization feasibility...............................................................................................................................
  • 3.3. Technical Feasibility....................................................................................................................................
  • 3.4. Schedule Feasibility....................................................................................................................................
• D. Describe how technical solutions can be compared (P4)..................................................................................
• 1. What is a requirements.....................................................................................................................................
• 2. Types of requirements.......................................................................................................................................
  • 2.1. Functional requirements............................................................................................................................
  • 2.2. Non-functional requirements.....................................................................................................................
• 3. How to determine requirements.......................................................................................................................
• 4. Requirements elicitation techniques.................................................................................................................
  • 4.1. Interviews...................................................................................................................................................
  • 4.2. Joint Application Development (JAD).........................................................................................................
  • 4.3. Questionnaires...........................................................................................................................................
  • 4.4. Document Analysis.....................................................................................................................................
  • 4.5. Observation................................................................................................................................................
• 5. Comparison of requirements elicitation techniques.........................................................................................
• Interviews..............................................................................................................................................................
• Joint Application Design........................................................................................................................................
• Questionnaires......................................................................................................................................................
• Document Analysis................................................................................................................................................
• Observation...........................................................................................................................................................
• Type of information...............................................................................................................................................
• As-is, improvements, to-be...................................................................................................................................
• As-is, improvements, to-be...................................................................................................................................
• As-is, improvements..............................................................................................................................................
• As-is.......................................................................................................................................................................
• As-is.......................................................................................................................................................................
• Depth of information.............................................................................................................................................
• High.......................................................................................................................................................................
• High.......................................................................................................................................................................
• Medium.................................................................................................................................................................
• Low........................................................................................................................................................................
• Low........................................................................................................................................................................
• Breadth of information..........................................................................................................................................
• Low Medium..........................................................................................................................................................
• High.......................................................................................................................................................................
• High.......................................................................................................................................................................
• High.......................................................................................................................................................................
• Low........................................................................................................................................................................
• Integration of information.....................................................................................................................................
• Low........................................................................................................................................................................
• High.......................................................................................................................................................................
• Low........................................................................................................................................................................
• Low........................................................................................................................................................................
• Low........................................................................................................................................................................
• User involvement..................................................................................................................................................
• Medium.................................................................................................................................................................
• High.......................................................................................................................................................................
• Low........................................................................................................................................................................
• Low........................................................................................................................................................................
• Low........................................................................................................................................................................
• Cost.......................................................................................................................................................................
• Medium.................................................................................................................................................................
• Low-Medium.........................................................................................................................................................
• Low........................................................................................................................................................................
• Low........................................................................................................................................................................
• Low-Medium.........................................................................................................................................................
• Figure-1: SDLC....................................................................................................... List of Figure
• Figure-2: Waterfall model.......................................................................................
• Figure-3: R-O-S-E...................................................................................................
• Figure-4: Incremental development........................................................................
• Figure-5: Spiral model.............................................................................................
• Figure-6: Feasibility................................................................................................
• Figure-7: Economic feasibility................................................................................
• Figure-8: Organizational feasibility........................................................................
• Figure-9: Requirements...........................................................................................
• Figure-10: Functional requirements........................................................................
• Figure-11: Non-functional requirements.................................................................
• Figure-12: Interviews..............................................................................................
• Figure-13: JAD........................................................................................................
• Figure-14: Questionnaires.......................................................................................
• Figure-15: Document Analysis................................................................................
• Figure-16: Observation............................................................................................

ASSIGNMENT 1 ANSWERS

A. Describe two iterative and two sequential software life cycle models (P1).

1. Introduction to System development lifecycle.

1.1. Definition of System Development Life Cycle (SDLC).

• System Development Life Cycle is also known as Application

Development Lifecycle or Software Development Lifecycle. It is

the process of planning, developing, testing and implementing a

specific information system.

Figure 1: SDLC

1.2. Purposes of SDLC.

• The System Development Life Cycle typically comprises six distinct

stages and is adaptable to a number of software and hardware

combinations. Analysis, design, development, testing,

implementation, documentation, and evaluation are the stages

that comprise this process.

2. Two sequential software lifecycle models.

2.1. Waterfall model.

2.1.1. Definition.

• The Waterfall Approach was the first commonly used SDLC Model

in software engineering to assure project success. The entire

P a g e | 1

software development process is split into several phases using

"The Waterfall" technique. Typically, the results of one step in this

waterfall model serve as the input for the subsequent phases in

turn.

Figure 2: Waterfall model

• The Waterfall model’s successive phrases are:

o Requirement Gathering and Analysis : During this stage, all

potential system needs are gathered and outlined in a

requirement specification document.

o System Design : In this phase, the required specifications

from the previous phase are examined, and the system

design is created. This system design aids in determining the

overall system architecture as well as the hardware and

system requirements.

o Implementation : In this phase, the required specifications

from the previous phase are examined, and the system

design is created. This system design aids in determining the

overall system architecture as well as the hardware and

system requirements.

o Verification : Following the testing of each unit created

P a g e | 2

high probability of requirements changing. So, with this

process model, risk and uncertainty are considerable.

o It takes till the end of the life cycle for any functioning

software to be generated.

o Adjusting scope during the life cycle can end a project.

2.1.4. When to use.

• The Waterfall Model is suitable for projects that have predictable

procedures, consistent and well-defined needs, big and complex

projects, a clear end goal, government or regulated sectors, and

limited funds and resources.

2.2. Reuses – Oriented Software Engineering.

2.2.1. Definition.

• The concepts and criteria for reusing the existing software serve

as the foundation for reuse software engineering.

Figure 3: R-O-S-E

• Requirements Specification and System Validation stages are

general process used in different software process but other

stages used in this model are different.

• Component Analysis : Component is chosen to implement

provided need in accordance with requirement definition. It is

unlikely that the chosen component will give all functionality,

however it is feasible that the component will provide some of the

necessary functionality.

• Requirements Modification : To analyze the requirement P a g e | 4

definition, information about the component that was chosen

during the component analysis is used. Requirements are changed

based on the components that are available. If the requirements

need to be changed, the component analysis process is utilized

again to discover a comparable solution.

• System Design : This phase sees the development of the system's

design. While organizing the framework, the designer must take

the reused component into account. When reusable components

are not available, new software is created.

• Development and Integration : To create new software, COTS

systems and components are merged. In this paradigm,

integration is a component of development rather than a distinct

endeavor.

2.2.2. Advantages

• Because many of the system's components are premade, reusing

software needs less work.

• The development team can save time by reusing the pre-made

components.

• Time and effort savings result in lower total costs.
• When you are given ready-made components, you may

concentrate on the brand-new components that are not yet

available.

• Reusing software frees up time that may be spent on ensuring and

maintaining the quality of software.

2.2.3. Disadvantages

• The genuine application of the reuse-oriented approach is not

always put into effect.

• Compromises in requirements might result in a system that

doesn't meet user needs.

P a g e | 5