Scribd
Upload
126 views4 pages

Question #1: Spiral Model

The spiral model combines iterative development with sequential linear development, allowing for incremental product releases. Each iteration involves identifying objectives, alternatives, constraints, and risks before proceeding to the next phase. The rational unified process divides a project into four stages: inception, elaboration, construction, and transition. It employs six core workflows - requirements, design, implementation, testing, deployment, and configuration/change management - throughout each stage. Key activities are focused at different stages; for example, business modeling occurs mainly in early stages. Risks in software projects can be categorized as project risks, product risks, or business risks. Project risks involve schedule, budget, resources, or customer-related issues. Product risks relate to development,

Uploaded by

sadia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
126 views4 pages

Question #1: Spiral Model

The spiral model combines iterative development with sequential linear development, allowing for incremental product releases. Each iteration involves identifying objectives, alternatives, constraints, and risks before proceeding to the next phase. The rational unified process divides a project into four stages: inception, elaboration, construction, and transition. It employs six core workflows - requirements, design, implementation, testing, deployment, and configuration/change management - throughout each stage. Key activities are focused at different stages; for example, business modeling occurs mainly in early stages. Risks in software projects can be categorized as project risks, product risks, or business risks. Project risks involve schedule, budget, resources, or customer-related issues. Product risks relate to development,

Uploaded by

sadia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Question #1

Spiral Model:
The spiral model blends the concept of iterative growth with the waterfall model's systematic,
controllable aspects. This Spiral model is a combination of the iterative process development
model with the sequential linear development model i.e. the waterfall model with a very high-
risk analysis focus. It allows for incremental product launches or incremental improvements with
any iteration around the spiral.

The rational unified process:


It is an agile technique for software development. RUP divides the life cycle of the Project into
four stages. The six main technology disciplines-, requirements, research and design,
implementation, testing and delivery-during each of the phases. Many procedures, however, are
more critical and take up more time at each point. For example, business modeling occurs mainly
during the early stages, start-up, and growth. Each of the four stages has the main objective,
which must be completed before the project can progress to the next level.

Question #2
(a)

Functionality of the login system


So in the given diagram we can deduce the diagram by the activities performs by the different actors In
this question there are three actors 1. customer,2.theif 3.cracker

Now first we discuss how a customer interact with the system

there are only four cases for the customer

1.he/she can deposit funds

2.he/she can withdraw funds

3.he/she can transfer funds

4.1.he/she can query balance

Now talking about security case

in the security case all the accounts of the customers are managed and the privicy is properly ensured ,the
govering body has proper access and control over the system ,and is ensuring proper integrity to the
cusmer

Now in the case of missue

Talking about the theif


privacy is envated and the integerity of the system is compromised , sapoofing in the user databse is done
and the control and the access is not in the govering subsidary,high chances of fraud.

Talking about the cracker

spoofing of the user is done to enter in the system database then manipulating all the information and the
privacy of the system is compromised.

the integrity of the system is destroyed and high chances of misusing the info in other site and stealing of
the money is done.

Question #2
(b)
Intangibility basically means things which cannot be touched. Same is in the case of Software systems.
This intangible nature of the software systems makes it hard for us to check its current status of progress,
the various other requirements, thus causing problems in planning, scheduling, budgeting etc. Testing of
all the phases sometimes becomes difficult because of all this. Therefore, one can say, the intangibility of
software systems possesses special problems for software project management.

The work of the managers and the codes is a way too different. The programmers may be very good at
writing various codes but software managers require very good managerial skills as they have to do a lot
of jobs like scheduling, assigning and identifying various resources, identifying various risks etc. These
are the things in which the coder lacks. Although they have some knowledge regarding that but to be a
successful software manager, one needs to have great hands on all these skills.

Question 3
In software management we will face lot of risks. A risk is a unwanted problem that we face in
our software project.
Risks are classified into 3 types
1. project risks

2. product risks

3. business risks

project risks

Risks related to budget, schedule, resources and customer related risks is called project risks.

For example: In a project if we allot 1 year but it takes more time than required is called project
risks.

To mitigate the risk we need to maintain proper and perfect planning.

we have to prepare for alternatives also if we has any issues.


Product risks

Issues related to development, testing , deployment is called product issues.

For example: if we face many errors and difficult to debug it is called product risks.

Business risks

This type of risks contain risks of building an excellent product that no one need, losing
budgetary or personnel commitments, etc.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy