Unit 9: Software Development Life Cycle

ASSIGNMENT 1

Learner’s name: Ninh Xuân Bảo Hưng

ID:GCS200058
Class: GCS0905A
Subject code: 1631
Assessor name: Võ Ngọc Mai

Assignment due: 6/6/2022

Assignment submitted: 6/6/2022
 ASSIGNMENT 2 FRONT SHEET

Qualification BTEC Level 5 HND Diploma in Computing

Unit number and title Unit 09: Software Development Life Cycle

Submission date Date Received 1st submission

Re-submission Date Date Received 2nd submission

Student Name Ninh Xuân Bảo Hưng Student ID GCS200058

Class GCS0905A Assessor name Vo Ngoc Mai

Student declaration

I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that
making a false declaration is a form of malpractice.

Student’s signature

Grading grid

P1 P2 P3 P4 M1 M2 M3 D1
 Summative Feedback:  Resubmission Feedback:

Grade: Assessor Signature: Date:

Signature & Date:

Page 3
 ASSIGNMENT 1 BRIEF
Qualification BTEC Level 5 HND Diploma in Computing

Unit number Unit 9: Software Development Life Cycle

Assignment title Planning a software development lifecycle

Academic Year 2022-2023

Unit Tutor Vo Ngoc Mai

Issue date Submission date

Name and date

Submission 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
Format:
and margins to be as follows: left = 1.25cm, right = 1cm, top = 1cm, bottom = 1cm. Citation
and references must follow the Harvard referencing style.
Word limit: 2000 words

You must submit the assignment by the due date and follow the submission method
Submission: specified by the Tutor. The submission form is soft copy, which is to be uploaded to the
following URL: http://cms.greenwich.edu.vn.

Your assignment must be your own work, and not copied by or from another student or from
other sources, such as book etc. If you use ideas, quotes or data (such as diagrams) from
Note: books, journals or other sources, you must reference the sources, using the Harvard style.
Make sure that you know how to reference properly and that you understand the plagiarism
guidelines. Plagiarism is a very serious offence, which will result in a failing grade.

Unit Learning Outcomes:

LO1 Describe different software development lifecycles.

LO2 Explain the importance of a feasibility study.

Assignment Brief and Guidance:

Page 4
System Scenario

Tune Source is a company headquartered in southern California. Tune Source is the brainchild of three
entrepreneurs with ties to the music industry: John Margolis, Megan Taylor, and Phil Cooper. Originally,
John and Phil partnered to open a number of brick and mortar stores in southern California specialising in
hard-to-find and classic jazz, rock, country, and folk recordings. Megan soon was invited to join the
partnership because of her contacts and knowledge of classical music. Tune Source quickly became known
as the place to go to find rare audio recordings. Annual sales last year were $40 million with annual growth
at about 3%–5% per year. Tune Source currently has a website that enables customers to search for and
purchase CDs. This site was initially developed by an Internet consulting firm and is hosted by a prominent
local Internet Service Provider (ISP) in Los Angeles. The IT department at Tune Source has become
experienced with Internet technology as it has worked with the ISP to maintain the site.

System Request

Project Sponsor: Carly Edwards, Assistant Vice President, Marketing

Business Need: This project has been initiated to increase sales by creating the capability of selling digital
music downloads to customers through kiosks in our stores, and over the Internet using our website.
Business Requirements: Using the Web or in-store kiosks, customers will be able to search for and
purchase digital music downloads. The specific functionality that the system should have includes the
following:
1. Search for music in our digital music archive.
2. Listen to music samples.
3. Purchase individual downloads at a fixed fee per download.
4. Establish a customer subscription account permitting unlimited downloads for a monthly fee.
5. 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:
6. $757,500 in sales from individual music downloads
7. $950,000 in sales from customer subscriptions
8. $205,000 in additional in-store or website CD sales
9. $153,000 in sales from music download gift cards
Special Issues or Constraints:

Page 5
 10. 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 underutilised.
11. 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.
12. 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:
13. (P1) Describe the following SDLC models: waterfall, prototyping, agile and spiral. Choose one that
you think suitable for the project and explain why.
[MV]
 Introduce SDLC in general
 Introduce 4 models
 Apply to Tune Source project
(M1) Discuss the suitability of each of the SDLC models for the project. For each model, specify
whether it is most, moderately or least suitable.
(D1) Discuss the merits of applying the waterfall model to a large software development project.
14. (P2) Identify some risks in Tune Source project and discuss an approach to manage them.
[MV]
 Introduce project risks in general
 Apply to TS project, provide at least 4 Risk assessment forms

Task 2 – Feasibility study

15. (P3) Discuss the purpose of conducting a feasibility study for the project.
[MV]
 Introduce feasibility study/ report in general
 Discuss the purpose of conducting a feasibility study
 Apply to TS
16. (P4) Discuss how the three feasibility criteria (technical, economic, organisational) are applied to
the project. Discuss whether the project is feasible.

Page 6
 Discuss alternative technical solutions using the alternative matrix.

[MV]
 Add introduction for this section
 Conduct feasibility study for TS project
 Confirm the project is feasible for 3 aspects (technical, economic, organisational) and explain why
 Provide an alternative matrix for Tune Source project:
- Intro this section
- Introduce details of each option below:
a. ASP.NET technology
b. Java Script technology
c. PHP technology
- Provide Weighted Alternative Matrix for those 3 options
- Select a solution for TS and explain why.
17. (M2) Explain the components of a feasibility report.
18. (D2) Assess the impact of each feasibility criterion on a software investigation.

Page 7
 Learning Outcomes and Assessment Criteria

Pass Merit Distinction

LO1 Describe different software development lifecycles

P1 Describe two iterative and

two sequential software D1 Assess the merits of applying
lifecycle models. M1 Describe, with an example, the Waterfall lifecycle model to a
why a particular lifecycle model large software development project.
is selected for a development
P2 Explain how risk is environment.
managed in the Spiral lifecycle
model.

LO2 Explain the importance of a feasibility study

P3 Explain the purpose of a D2 Assess the impact of different

feasibility report. feasibility criteria on a software
M2 Discuss the components of a investigation.
feasibility report.
P4 Describe how technical
solutions can be compared.

Page 8
Unit 9: Software Development Life Cycle ASSIGNMENT 1 ........................................................................... 1
P1 Describe two iterative and two sequential software lifecycle models. ...................................................... 10
1. Introduction SDLC. ................................................................................................................................. 10
2. Iterative and Sequential software lifecycle model. .................................................................................. 13
3. Apply to tune source ................................................................................................................................ 24
P2 Identify some risks in Tune Source project and discuss an approach to manage them. ............................ 24
1. What is Risk? ........................................................................................................................................... 24
2. What is Risk Management process? ........................................................................................................ 24
3. Risk Management process ....................................................................................................................... 24
4. Why is risk assessment important? .......................................................................................................... 25
5. Apply risk to TS project .......................................................................................................................... 25
P3 Discuss the purpose of conducting a feasibility study for the project. ....................................................... 28
1. What is a feasibility report? ..................................................................................................................... 28
2. The importance of feasibility report? ...................................................................................................... 28
3. The purpose of the feasibility report? ...................................................................................................... 28
4. Type fesibility: ......................................................................................................................................... 28
5. Apply feasibility study to TS ................................................................................................................... 29
P4 Discuss how the three feasibility criteria (technical, economic, organisational) are applied to the project.
Discuss whether the project is feasible ............................................................................................................ 29
Discuss alternative technical solutions using the alternative matrix. .............................................................. 29
1. Confirm the project is feasible for 3 aspects (technical, economic, organisational) and explain why .... 29
2. What is alternative matrix ........................................................................................................................ 30
3. ASP.NET technology .............................................................................................................................. 30
4. Java Script technology ............................................................................................................................. 31
5. PHP technology ....................................................................................................................................... 31
6. Weighted Alternative matrix for 3 choices .............................................................................................. 31

Page 9
P1 Describe two iterative and two sequential software lifecycle models.

1. Introduction SDLC.
SDLC stands for Software Development Life Cycle. It is a process that gives a complete idea about
developing, designing, and maintaining a software project by ensuring that all the functionalities along with
user requirements, objectives, and end goals are addressed. With SDLC, the software project’s quality and
the overall software development process get enhanced.

Page 10
 a. Stages of SDLC

Stage 1: Requirement Gathering & Analysis Phase

- In an SDLC, this is the first and most crucial phase for a software project’s success. In this phase,
communication takes place between stakeholders, end-users, and project teams, as both functional and non-
functional requirements are gathered from customers.

The Requirement Gathering & Analysis Phase of SDLC involves the following:
+ Analysis of functionality and financial feasibility
+ Identifying and capturing requirements of stakeholders through customer interactions like interviews,
surveys, etc.
+ Clearly defining and documenting customer requirements in an SRS (Software Resource Specification
Document) comprising of all product requirements that need to be developed
+ Creating project prototypes to show the end-user how the project will look

Stage 2: Design Phase

- In the design phase of an SDLC, the architectural design is proposed for the project based on the SRS
Document requirements.

The Designing Phase of SDLC involves the following:

+ Separation of hardware and software system requirements
+ Designing the system architecture based on gathered requirements
+ Creating Unified Modelling Language (UML) diagrams like- use cases, class diagrams, sequence
diagrams, and activity diagrams

Page 11
 Stage 3: Development Phase

- In the entire SDLC, the development phase is considered to be the longest one. In this phase, the actual
project is developed and built.

The Development Phase of SDLC involves the following:

+ Actual code is written
+ Demonstration of accomplished work presented before a Business Analyst for further modification of
work
+ Unit testing is performed, i.e., verifying the code based on requirements

Stage 4: Testing Phase

- Almost all stages of SDLC involves the testing strategy. However, SDLC’s testing phase refers to
checking, reporting, and fixing the system for any bug/defect. In this phase, the on-going system or project is
migrated to a test environment where different testing forms are performed. This testing continues until the
project has achieved the quality standards, as mentioned in the SRS document during the requirement
gathering phase.

The Testing Phase involves the following:

+ Testing the system as a whole
+ Performing different types of test in the system
+ Reporting and fixing all forms of bugs & defects

Stage 5: Deployment & Maintenance Phase

- In this SDLC phase, once the system testing has been done, it is ready to be launched. The system may be
initially released for limited users by testing it in a real business environment for UAT or User Acceptance
Testing.

The Deployment & Maintenance Phase involves the following:

+ The system is ready for delivery
+ The system is installed and used
+ Errors are rectified that might have been previously missed
+ Enhancing the system inside a data center

Page 12
 2. Iterative and Sequential software lifecycle model.
2.1. Sequential
- Sequential models such as Waterfall or Prototyping rely on intensive periods of collecting and refining
requirements for a product before design and development activity can take place. Products developed using
these models are intended to be complete when released to customers. Central to the approach is an
assumption that by adhering to the requirements captured at the outset, the product will fulfil the wishes of
those customers:

- Following are the most important and popular Sequential model :

+ Waterfall
+ Prototyping

a. Waterfall
- Waterfall approach was first SDLC Model to be used widely in Software Engineering to ensure success
of the project. In "The Waterfall" approach, the whole process of software development is divided into
separate phases. In this Waterfall model, typically, the outcome of one phase acts as the input for the next
phase sequentially.

Page 13
- The following illustration is a representation of the different phases of the Waterfall Model:

The sequential stages in the Waterfall model are:

Step 1 : Requirements gathering and analysis
- All possible requirements of the developed system are captured in this phase and documented in the
requirements specification document.

Step 2 : System Design

- The requirement specifications from first phase are studied in this phase and the system design is
prepared. This system design helps in specifying hardware and system requirements and helps in defining
the overall system architecture.

Step 3 : Implementation
- With inputs from the system design, the system is first developed in small programs called units, which
are integrated in the next phase. Each unit is developed and tested for its functionality, which is referred
to as Unit Testing.

Step 4 : Integration and Testing

- All the units developed in the implementation phase are integrated into a system after testing of each
unit. Post integration the entire system is tested for any faults and failures.

Step 5 : Deployment of system

- Once the functional and non-functional testing is done; the product is deployed in the customer
environment or released into the market.

Page 14
Step 6 : Maintenance
- There are some issues which come up in the client environment. To fix those issues, patches are
released. Also to enhance the product some better versions are released. Maintenance is done to deliver
these changes in the customer environment.

- All these phases are cascaded to each other in which progress is seen as flowing steadily downwards
(like a waterfall) through the phases. The next phase is started only after the defined set of goals are
achieved for previous phase and it is signed off, so the name "Waterfall Model". In this model, phases do
not overlap.

Waterfall Model - Application

- Every software developed is different and requires a suitable SDLC approach to be followed based on
the internal and external factors.
- Some situations where the use of Waterfall model is most appropriate are :
+ Requirements are very well documented, clear and fixed.
+ Product definition is stable.
+ Technology is understood and is not dynamic.
+ There are no ambiguous requirements.
+ Ample resources with required expertise are available to support the product.
+ The project is short.

Waterfall Model - Advantages

- The advantages of waterfall development are that it allows for departmentalization and control. A
schedule can be set with deadlines for each stage of development and a product can proceed through the
development process model phases one by one.
- Some of the major advantages of the Waterfall Model are as follows :
+ Simple and easy to understand and use
+ Easy to manage due to the rigidity of the model. Each phase has specific deliverables and a review
process.
+ Phases are processed and completed one at a time.
+ Works well for smaller projects where requirements are very well understood.
+ Clearly defined stages.
+ Well understood milestones.
+ Easy to arrange tasks.
+ Process and results are well documented.

Page 15
Waterfall Model - Disadvantages
- The disadvantage of waterfall development is that it does not allow much reflection or revision. Once an
application is in the testing stage, it is very difficult to go back and change something that was not well-
documented or thought upon in the concept stage.
- The major disadvantages of the Waterfall Model are as follows :
+ No working software is produced until late during the life cycle.
+ High amounts of risk and uncertainty.
+ Not a good model for complex and object-oriented projects.
+ Poor model for long and ongoing projects.
+ Not suitable for the projects where requirements are at a moderate to high risk of changing. So, risk and
uncertainty is high with this process model.
+ It is difficult to measure progress within stages.
+ Cannot accommodate changing requirements.
+ Adjusting scope during the life cycle can end a project.
+ Integration is done as a "big-bang. at the very end, which doesn't allow identifying any technological or
business bottleneck or challenges early.

b. Prototyping
- Prototyping Model is a software development model in which prototype is built, tested, and reworked
until an acceptable prototype is achieved. It also creates base to produce the final system or software. It
works best in scenarios where the project’s requirements are not known in detail. It is an iterative, trial
and error method which takes place between developer and client.
- The following illustration is a representation of the different phases of the Prototyping Model:

The sequential stages in the Prototyping model are:

Step 1: Requirements gathering and analysis
- A prototyping model starts with requirement analysis. In this phase, the requirements of the system are
defined in detail. During the process, the users of the system are interviewed to know what is their
expectation from the system.

Page 16
Step 2: Quick design
- The second phase is a preliminary design or a quick design. In this stage, a simple design of the system
is created. However, it is not a complete design. It gives a brief idea of the system to the user. The quick
design helps in developing the prototype.

Step 3: Build a Prototype

- In this phase, an actual prototype is designed based on the information gathered from quick design. It is
a small working model of the required system.

Step 4: Initial user evaluation

- In this stage, the proposed system is presented to the client for an initial evaluation. It helps to find out
the strength and weakness of the working model. Comment and suggestion are collected from the
customer and provided to the developer.

Step 5: Refining prototype

- If the user is not happy with the current prototype, you need to refine the prototype according to the
user’s feedback and suggestions.
- This phase will not over until all the requirements specified by the user are met. Once the user is
satisfied with the developed prototype, a final system is developed based on the approved final prototype.

Step 6: Implement Product and Maintain

- Once the final system is developed based on the final prototype, it is thoroughly tested and deployed to
production. The system undergoes routine maintenance for minimizing downtime and prevent large-scale
failures.

Prototype Model - Advantages

Here, are important pros/benefits of using Prototyping models:
+ Users are actively involved in development. Therefore, errors can be detected in the initial stage of the
software development process.
+ Missing functionality can be identified, which helps to reduce the risk of failure as Prototyping is also
considered as a risk reduction activity.
+ Helps team member to communicate effectively
+ Customer satisfaction exists because the customer can feel the product at a very early stage.
+ There will be hardly any chance of software rejection.
+ Quicker user feedback helps you to achieve better software development solutions.
+ Allows the client to compare if the software code matches the software specification.
+ It helps you to find out the missing functionality in the system.
+ It also identifies the complex or difficult functions.
+ Encourages innovation and flexible designing.

Page 17
+ It is a straightforward model, so it is easy to understand.
+ No need for specialized experts to build the model
+ The prototype serves as a basis for deriving a system specification.
+ The prototype helps to gain a better understanding of the customer’s needs.
+ Prototypes can be changed and even discarded.
+ A prototype also serves as the basis for operational specifications.
+ Prototypes may offer early training for future users of the software system.

Prototype Model - Disadvantages

Here, are important cons/drawbacks of prototyping model:
+ Prototyping is a slow and time taking process.
+ The cost of developing a prototype is a total waste as the prototype is ultimately thrown away.
+ Prototyping may encourage excessive change requests.
+ Some times customers may not be willing to participate in the iteration cycle for the longer time
duration.
+ There may be far too many variations in software requirements when each time the prototype is
evaluated by the customer.
+ Poor documentation because the requirements of the customers are changing.
+ It is very difficult for software developers to accommodate all the changes demanded by the clients.
+ After seeing an early prototype model, the customers may think that the actual product will be delivered
to him soon.
+ The client may lose interest in the final product when he or she is not happy with the initial prototype.
+ Developers who want to build prototypes quickly may end up building sub-standard development
solutions.

Page 18
 2.1. Iterative
- This is in contrast with iterative ways of working, with an emphasis on delivering less complex products,
often to test customer response before making adjustments. The techniques encourage regular feedback from
customers, and rapid response to that feedback; refining ideas and revisiting design and development
activities with the intention of delivering products which better reflect what customers want:

- Following are the most important and popular Iterative model :

+ Spiral
+ Agile

a. Spiral
- Spiral model is one of the most important Software Development Life Cycle models, which provides
support for Risk Handling. In its diagrammatic representation, it looks like a spiral with many loops. The
exact number of loops of the spiral is unknown and can vary from project to project. Each loop of the
spiral is called a Phase of the software development process. The exact number of phases needed to
develop the product can be varied by the project manager depending upon the project risks. As the project
manager dynamically determines the number of phases, so the project manager has an important role to
develop a product using the spiral model.
- The Radius of the spiral at any point represents the expenses(cost) of the project so far, and the angular
dimension represents the progress made so far in the current phase.

Page 19
- The following illustration is a representation of the different phases of the Spiral Model :

- The spiral model has four phases. A software project repeatedly passes through these phases in
iterations called Spirals.
Step 1 : Identification
- This phase starts with gathering the business requirements in the baseline spiral. In the subsequent
spirals as the product matures, identification of system requirements, subsystem requirements and unit
requirements are all done in this phase.
- This phase also includes understanding the system requirements by continuous communication between
the customer and the system analyst. At the end of the spiral, the product is deployed in the identified
market.

Step 2 : Design
- The Design phase starts with the conceptual design in the baseline spiral and involves architectural
design, logical design of modules, physical product design and the final design in the subsequent spirals.

Step 3 : Construct or Build

- The Construct phase refers to production of the actual software product at every spiral. In the baseline
spiral, when the product is just thought of and the design is being developed a POC (Proof of Concept) is
developed in this phase to get customer feedback.
- Then in the subsequent spirals with higher clarity on requirements and design details a working model
of the software called build is produced with a version number. These builds are sent to the customer for
feedback.

Page 20
Step 4 : Evaluation and Risk Analysis
- Risk Analysis includes identifying, estimating and monitoring the technical feasibility and management
risks, such as schedule slippage and cost overrun. After testing the build, at the end of first iteration, the
customer evaluates the software and provides feedback.

Spiral Model - Application

- The Spiral Model is widely used in the software industry as it is in sync with the natural development
process of any product, i.e. learning with maturity which involves minimum risk for the customer as well
as the development firms.
- The following pointers explain the typical uses of a Spiral Model :
+ When there is a budget constraint and risk evaluation is important.
+ For medium to high-risk projects.
+ Long-term project commitment because of potential changes to economic priorities as the requirements
change with time.
+ Customer is not sure of their requirements which is usually the case.
+ Requirements are complex and need evaluation to get clarity.
+ New product line which should be released in phases to get enough customer feedback.
+ Significant changes are expected in the product during the development cycle.

Spiral Model - Advantages

- The advantage of spiral lifecycle model is that it allows elements of the product to be added in, when
they become available or known. This assures that there is no conflict with previous requirements and
design.
- The advantages of the Spiral SDLC Model are as follows :
+ Changing requirements can be accommodated.
+ Allows extensive use of prototypes.
+ Requirements can be captured more accurately.
+ Users see the system early.
+ Development can be divided into smaller parts and the risky parts can be developed earlier which helps
in better risk management.

Spiral Model - Disadvantages

- The disadvantages of the Spiral SDLC Model are as follows −
+ Management is more complex.
+ End of the project may not be known early.
+ Not suitable for small or low risk projects and could be expensive for small projects.
+ Process is complex
+ Spiral may go on indefinitely.
+ Large number of intermediate stages requires excessive documentation.

Page 21
b. Agile
- Agile SDLC model is a combination of iterative and incremental process models with focus on process
adaptability and customer satisfaction by rapid delivery of working software product. Agile Methods
break the product into small incremental builds. These builds are provided in iterations. Each iteration
typically lasts from about one to three weeks. Every iteration involves cross functional teams working
simultaneously on various areas like :
+ Planning
+ Requirements Analysis
+ Design
+ Coding
+ Unit Testing and
+ Acceptance Testing.

Here is a graphical illustration of the Agile Model :

Step 1 : Requirements gathering

- In this phase, you must define the requirements. You should explain business opportunities and plan the
time and effort needed to build the project. Based on this information, you can evaluate technical and
economic feasibility.

Step 2 : Design the requirements

- When you have identified the project, work with stakeholders to define requirements. You can use the
user flow diagram or the high-level UML diagram to show the work of new features and show how it will
apply to your existing system.

Page 22
Step 3 : Construction/ iteration
- When the team defines the requirements, the work begins. Designers and developers start working on
their project, which aims to deploy a working product. The product will undergo various stages of
improvement, so it includes simple, minimal functionality.

Step 4 : Testing
- In this phase, the Quality Assurance team examines the product's performance and looks for the bug.

Step 5 : Deployment
- In this phase, the team issues a product for the user's work environment.

Step 6 : Feedback
- After releasing the product, the last step is feedback. In this, the team receives feedback about the
product and works through the feedback.

Agile Model - Advantage

- Agile methods are being widely accepted in the software world recently. However, this method may not
always be suitable for all products. Here are some pros and cons of the Agile model.
- The advantages of the Agile Model are as follows :
+ Is a very realistic approach to software development.
+ Promotes teamwork and cross training.
+ Functionality can be developed rapidly and demonstrated.
+ Resource requirements are minimum.
+ Suitable for fixed or changing requirements
+ Delivers early partial working solutions.
+ Good model for environments that change steadily.
+ Minimal rules, documentation easily employed.
+ Enables concurrent development and delivery within an overall planned context
+ Little or no planning required.
+ Easy to manage.
+ Gives flexibility to developers.

Page 23
 Agile Model - Disadvantage
The disadvantages of the Agile Model are as follows −
+ Not suitable for handling complex dependencies.
+ More risk of sustainability, maintainability and extensibility.
+ An overall plan, an agile leader and agile PM practice is a must without which it will not work.
+ Strict delivery management dictates the scope, functionality to be delivered, and adjustments to meet
the deadlines.
+ Depends heavily on customer interaction, so if customer is not clear, team can be driven in the wrong
direction.
+ There is a very high individual dependency, since there is minimum documentation generated.
+ Transfer of technology to new team members may be quite challenging due to lack of documentation.

3. Apply to tune source

- In the 4 Life Cycles of Software Development including waterfall, prototyping, agile and spiral. I find
that the tuned source project fits the Agile model best. I choose Agile project because: as far as I know
this model is very popularly used in software companies and it is also a popular model. Because it
responds to customer needs quickly, changes can be made if the customer changes their mind, and the
customer can view each finished product within 1 to 4 weeks of product difficulty. there. . It brings many
benefits to the investor such as being able to drop the project if the customer changes without spending
too much effort of the programmer, it also increases the value and transparency of the business. It gives
flexibility to developers.

P2 Identify some risks in Tune Source project and discuss an approach to manage them.
1. What is Risk?
- Risk implies future uncertainty about deviation from expected earnings or expected outcome. Risk
measures the uncertainty that an investor is willing to take to realize a gain from an investment.

2. What is Risk Management process?

- A risk management process in projects is a logical sequence of procedures implemented by decision
makers in order to keep the project on track under particular scenarios. Decision-makers must identify,
assess, and evaluate risks throughout the project's life cycle, and then utilize their organizational structure
and administrative processes to mitigate those risks in favor of the project. Project complexity and
organizational maturity are seen as major elements that might influence project success.

3. Risk Management process

a) Identifying risks
Risk identification is the process of identifying and assessing threats to an organization, its operations and
its workforce. For example, risk identification may include assessing IT security threats such as malware

Page 24
and ransomware, accidents, natural disasters and other potentially harmful events that could disrupt
business operations.

b) Risk analysis and assessment

Risk analysis involves establishing the probability that a risk event might occur and the potential outcome
of each event. Risk evaluation compares the magnitude of each risk and ranks them according to
prominence and consequence.

c) Risk mitigation and monitoring

Risk mitigation refers to the process of planning and developing methods and options to reduce threats to
project objectives. A project team might implement risk mitigation strategies to identify, monitor and
evaluate risks and consequences inherent to completing a specific project, such as new product creation.
Risk mitigation also includes the actions put into place to deal with issues and effects of those issues
regarding a project.

4. Why is risk assessment important?

- Risk assessments are critical because they are a component of an occupational health and safety
management strategy. They aid in the creation of awareness of hazards and risks.
• Determine who may be at danger (e.g., employees, cleaners, visitors, contractors, the public, etc.).
• Determine if a specific danger necessitates the implementation of a control scheme.
• Determine if current control measures are adequate or whether more should be done.
• Preventing injuries or diseases is extremely important when done at the design or planning stages.
• Determine the importance of dangers and control methods.
• Comply with all applicable legal obligations.

5. Apply risk to TS project

a. Introduction
Because the company is currently short of many things such as resources, funding, epidemics, and many
other things, leading to risks that the company cannot avoid such as being currently in the covid 19
epidemic. It makes most of the employees have to sick leave. Or that there are a lot of employees who
lack work experience. Then it can slows down the completion rate of the process.

b. 4 Risk assessment forms

Page 25
 Risk 1# The development of this system may be slowed down because of the
spread of covid 19, and as a result, some team members have taken
time off due to fear of illness.

Likelihood of risk Moderate probability of risk

Potential impact on the project This risk can increase the time to complete installation tasks by up to
25%.

Way to address this risk

Employee leave is very important to the speed of the project. To be able to ensure the safety of all employees
and still be able to continue the progress of the project. We must let employees borrow computers from the
company to work from home and pay reasonable wages so that employees are motivated to accelerate the
process of the project

Risk 2# The development of this system may be slowed down because of the
inexperience of the team members. Because I don't have much
experience in programming.

Likelihood of risk High probability of risk

Potential impact on the project This risk can increase the time to complete installation tasks by up to
70%.

Way to address this risk

This is very important for the completion of the tune source project. It can last a very long time from 2 to 4
months. To overcome this, we need to get employees to do their jobs right so that they can easily complete
their own work. Or We will alternate jobs and train employees on things they don't know to shorten project
completion time.

Page 26
 Risk 3# Because the company's schedule is not suitable, the project time may
be longer from 1 to 2 months

Likelihood of risk Minor probability of risk

Potential impact on the project This risk can increase the time to complete installation tasks by up to
60%.

Way to address this risk

To overcome the situation that the company's operating schedule is not suitable. We must train managers so
that they have a lot of experience in scheduling different projects. Because the schedule of activities greatly
affects the completion of the projects. To be able to complete the project as quickly as possible, the manager
must arrange the time carefully.

Risk 4# Hacker attack on the system

Likelihood of risk The probability of error is high

Potential impact on the project This risk can increase the time to complete installation tasks by up to
50%.

Way to address this risk

Nowadays, because of the development of technology, hackers can easily hack into the project to get a lot of
information. It brings a lot of disadvantages to us. To be able to overcome that, we must train the top system
security staff so that they can not be attacked by hackers and take away data.

Page 27
P3 Discuss the purpose of conducting a feasibility study for the project.
1. What is a feasibility report?
- A feasibility Study is a formal project document that shows results of the analysis, research and
evaluation of a proposed project and determines if this project is technically feasible, cost-effective and
profitable.
- A feasibility study may entail a substantial shift in how a firm works, such as the acquisition of a
competitor, in some situations. As a result, the feasibility study may include a cash flow analysis, which
compares the amount of cash generated by revenue to the project's operational expenses. A risk
assessment must also be completed to determine whether the return is sufficient to compensate for the
level of risk associated with the venture.

2. The importance of feasibility report?

- The importance of a feasibility study is based on organizational desire to “get it right” before
committing resources, time, or budget. A feasibility study might uncover new ideas that could completely
change a project’s scope. It’s best to make these determinations in advance, rather than to jump in and to
learn that the project won’t work. Conducting a feasibility study is always beneficial to the project as it
gives you and other stakeholders a clear picture of the proposed project.

3. The purpose of the feasibility report?

- The purpose of the feasibility report is to present the project parameters and define the potential
solutions to the defined problem, need, or opportunity. Having brainstormed a variety of potential
solutions, the project team expands on each of these potential solutions, providing sufficient detail,
including very high-level costing information, to permit the project leader to recommend to the approving
authority all of the viable potential solutions that should be further analyzed in the next phase (Business
Case). Project constraints and limitations of expenditure are among the various factors that will determine
viability.

4. Type fesibility:
a) Technical Feasibility Study
- Technical feasibility is a standard practice for companies to conduct feasibility studies before
commencing work on a project. Businesses undertake a technical feasibility study to assess the
practicality and viability of a product or service before launching it. Whether you are working as a
product engineer, product designer or team manager, there may be plenty of situations in your career
where you have to prepare a technical feasibility study.

Page 28
 b) Economic Feasibility Study
- The economic feasibility step of business development is that period during which a break-even
financial model of the business venture is developed based on all costs associated with taking the product
from idea to market and achieving sales sufficient to satisfy debt or investment requirements.

c) Operational Feasibility
- Operational feasibility is the measure of how well a proposed system solves the problems, and takes
advantage of the opportunities identified during scope definition and how it satisfies the requirements
identified in the requirements analysis phase of system development.

5. Apply feasibility study to TS

- For the "tune source" project to work at its best, we need to have a feasibility study first. It shows the
results and evaluation of the "tune source" project. From there, the project can be determined in terms of
technique, cost and profitability of the project. In order to provide solutions to the problem of
opportunity. Increase revenue and fulfill the plans set forth by the company. To compete with the market.

P4 Discuss how the three feasibility criteria (technical, economic, organisational) are applied to the project.
Discuss whether the project is feasible

Discuss alternative technical solutions using the alternative matrix.

1. Confirm the project is feasible for 3 aspects (technical, economic, organisational) and explain why
Technical feasibility
- Technical feasibility in "Tune Source" is for technical research and practical evaluation of the company's
products and services before bringing to the market.

Economic feasibility
- Economic feasibility helps the project identify the benefits and savings expected from the system and
compare them with the costs.
Economic feasibility of the project "tune suorce" :
a) Development Cost

Development Cost

Amount Development Cost Hour Cost

6 Programmer(50$/h) 360 hour 72.000$

1 Designer(60$/h) 200 hour 12.000$

Page 29
 1 Database(70$/h) 50 hour 3.500$

2 Tester(40$/h) 180 hour 7.200

2 Tranning (5.000$/ Student) 10.000

1 PC Sever (hardware) 5.000$

1 Software 1.000$

Total 110.700$

b) Tangible Cost

Tangible Cost

Amount Tangible Cost Cost

1 sales from individual music 757.500$

downloads

1 sales from customer subscriptions 950.000$

1 additional in-store or website CD 205.000$

sales

1 sales from music download gift 153.000$

cards

Total 2.065.500$

2. What is alternative matrix

- An Alternatives Evaluation Matrix can be used to compare alternatives for numerous requirements
including hardware, software, databases, operating systems, or languages.

-A Weighted Alternatives Evaluation Matrix, assigns weighting factors to criteria when comparing
alternatives

3. ASP.NET technology
- ASP.NET is a web development platform, which provides a programming model, a comprehensive software
infrastructure and various services required to build up robust web applications for PC, as well as mobile
devices.
- ASP.NET works on top of the HTTP protocol, and uses the HTTP commands and policies to set a browser-
to-server bilateral communication and cooperation.

Page 30
 4. Java Script technology
- JavaScript is a lightweight, cross-platform, and interpreted compiled programming language which is also
known as the scripting language for webpages. It is well-known for the development of web pages, many
non-browser environments also use it. JavaScript can be used for Client-side developments as well as
Server-side developments.

5. PHP technology
The term PHP is an acronym for PHP: Hypertext Preprocessor. PHP is a server-side scripting language
designed specifically for web development. It is open-source which means it is free to download and use. It
is very simple to learn and use. The files have the extension “.php”.

6. Weighted Alternative matrix for 3 choices

ASP.NET technology Java Script technology PHP technology

Criteria Weighting Score Weighted Score Weighted Score Weighted

Factor Score Score Score

Cost 5 3 15 2 10 1 5

Development Time 3 2 6 1 3 3 9

Maintenance Cost 2 3 6 2 4 2 4

Integration 1 3 3 2 2 3 3

Total Score 11 30 7 19 9 21

REFERENT
osarome.blogspot.com(2011) . 1. TECHNICAL FEASIBILITY 2. OPERATIONAL FEASIBILITY 3.
ECONOMIC FEASIBILITY.[online] Available at : https://osarome.blogspot.com/2011/10/1-technical-
feasibility-2-operational.html [Accessed 5 June 2022].
projectmanager.com (2021). What Is a Feasibility Study.[online] Available at :
https://www.projectmanager.com/training/how-to-conduct-a-feasibility-study [Accessed 5 June 2022].
simplilearn.com (2022). Feasibility Study And Its Importance in Project Management.[online] Available at :
https://www.simplilearn.com/feasibility-study-article [Accessed 4 June 2022]
investopedia.com (2022) . Risk .[online] Available at : https://www.investopedia.com/terms/r/risk.asp
[Accessed 4 June 2022]
tutorialspoint.com (2022). SDLC - Agile Model.[online] Available at :
https://www.tutorialspoint.com/sdlc/sdlc_agile_model.htm [Accessed 3 June 2022]

Page 31
tutorialspoint.com (2022). SDLC - Iterative Model.[online] Available at :
https://www.tutorialspoint.com/sdlc/sdlc_iterative_model.htm [Accessed 3 June 2022]
tutorialspoint.com (2022). SDLC - Spiral Model .[online] Available at :
https://www.tutorialspoint.com/sdlc/sdlc_spiral_model.htm [Accessed 3 June 2022]
tutorialspoint.com (2022). SDLC - Agile Model.[online] Available at :
https://www.tutorialspoint.com/sdlc/sdlc_agile_model.htm [Accessed 3 June 2022]

Page 32