Software Development Life Cycle for Tune Source, Assignments of Data Acquisition

Download Software Development Life Cycle for Tune Source and more Assignments Data Acquisition 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: DINH NGOC LONG

ID: GCS

Class: GCS1005A

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: 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.

Table of Contents

1.2 Purposes of SDLC

The purpose of an SDLC methodology is to provide IT Project Managers with the tools to help

ensure successful implementation of systems that satisfy University strategic and business

objectives.

+ Standardize the process for defining the tasks and outputs

+ Make sure you plan, estimate, and schedule the job.

+ Increase the rate of development Lower the risk of projects, strengthen client relationships, and

lower overall project management and production costs

2. Two sequential software lifecycle models

2.1 Waterfall model

2.1.1 Definition

The term "waterfall model" is often used. The Waterfall model, a project management approach based on a sequential and sequential design process, is regarded as one of the simplest project management models currently accessible. The project's phases are carried out sequentially under the Waterfall paradigm. Only once the prior phase is finished is a new one initiated. A straightforward waterfall model contains 6 stages:

• Request
• Design
• Execute (build)
• Verification
• Deployment
• Maintenance P a g e | 2

Figure: Waterfall Model Explain:

• Requirement Analysis: The team does a search for requirements related to the project.

• Determine which business need the project will address
• User requirements for the product developed by the project
• Constraints and associated risks.

• Design: The team creates the design for the product to address any design requirements, constraints, and goals. It will describe exactly how the logic of the system mentioned in the analysis will be implemented.
• Development: Products are built to support design.
• Test: Parts of the product are checked
• Deployment: The tested product actually works
• Maintenance: Is a short monitoring period. In which the project team solves customer problems

2.1.2 Advantages

• Adapts well to flexible groups
• Imposing a structured organization
• Allows for early design changes
• Suitable for landmark-oriented projects P a g e | 3

Figure: V-Model Explain:

• Requirements: Gather precise data, software specs from client requests.
• System design: choose the proper databases and programming languages
• Build phase: Run the program
• Test phase: ensure it was constructed in accordance with the customer's requirements.
• Application deployment: Run the program in a real-world setting.
• System maintenance: Upgrades and code modifications can be made in accordance with customer needs.

2.2.2 Advantages

• Easy to Understand.
• Testing Methods like planning, test designing happens well before coding.
• This saves a lot of time. Hence a higher chance of success over the waterfall model.
• Avoids the downward flow of the defects. P a g e | 5

• Works well for small plans where requirements are easily understood.

2.2.3 Disadvantages

• Very rigid and least flexible.
• Not a good for a complex project.
• Software is developed during the implementation stage, so no early prototypes of the software are produced.
• If any changes happen in the midway, then the test documents along with the required documents, has to be updated. 2.3.4 When to use
• Whenever the requirements are clear and unambiguous.
• For small to medium-sized projects with established, well specified needs, the V-shaped paradigm should be employed.
• When sample technical resources with crucial technical skills are available, the V-shaped model should be selected.

3. Two interative software lifecycle models

3.1 Incremental development

3.1.1 Definition

Each each iteration of the product improves on the one before it by introducing features that are visible to users. These are referred to as "vertical" increments (i.e., the difference between subsequent product versions), as opposed to the alternative technique, which involves delivering fully functional technical components one after the other. P a g e | 6

• Major criteria must be specified, although certain specifics can change over time.
• A product needs to reach the market quickly.
• There is a new technology in use.
• Resources with the necessary skill set are lacking.
• Some of the aims and characteristics are high risk.

3.2 Spiral model

3.2.1 Definition

In the spiral approach, risk analysis is given greater weight than in incremental system

development.

Figure: Spiral model

3.2.2 Advantages

• Early in the software life cycle, software is created. P a g e | 8

• The Spiral model is the greatest development model to use since it incorporates risk analysis and risk management at each stage, which is one of its key features.
• Adaptability in the demands. With this paradigm, needs may be precisely and readily changed at subsequent stages. Additionally, later on, more functionality can be added.
• Large and complicated projects benefit from it.
• It improves client satisfaction. At an early stage of the software development process, we may include clients in the creation of goods. Additionally, early in the software life cycle, software is developed.
• Strong documentation and approval controls.
• It is appropriate for high-risk projects where business requirements could be erratic. This may be used to create a product that is highly personalized.

3.2.3 Disadvantages

• Due of its high cost, it is not appropriate for minor projects.
• Compared to other SDLC models, it is considerably more sophisticated. Process is intricate.
• Too much reliance on risk analysis and the need for very specialized knowledge difficulty managing one's time. Time estimation is highly challenging since the project's beginning doesn't know how many phases there will be.
• Spiral may continue forever.
• The project's end may not be recognized right away.
• Low risk initiatives are not a good fit for it.
• Setting up measurable, objective benchmarks might be challenging. Numerous intermediary steps demand an unnecessary amount of paperwork.

3.2.4 When to use

• When a project is vast in software engineering, a spiral model is utilized.
• Spiral approach is utilized when frequent releases are necessary.
• When it is appropriate to create a prototype
• When evaluating risks and costs is crucial
• Spiral approach is beneficial for projects with moderate to high risk. P a g e | 9