Assignment
Course Title: Software Project V
Course Code: CSE317
Submitted To:
Ms. Chowdhury Abida Anjum Era
Daffodil International University
Submitted By:
Name: Afraz Ul Haque
ID: 192-15-13252
Section: F
University Campus Portal
Campus Basic information like Location, classroom buildings, admin buildings,
labs, and dormitories, etc. It has manual login and logout. Immediate access to all
campus information plus:
E-mail
Cell phone voice messaging
Text messaging
Project Scope
Project scope describes
The functions and features that are to be delivered to end-users.
The data that is input and output from the system.
The content that is presented to users as a consequence of using the
software.
The performance, constraints, interfaces, and reliability that bound the
system.
The scope can be defined using two techniques:
A narrative description of software scope is developed after
communication with all stakeholders.
A set of use cases is developed by end-users.
After the scope has been identified, two questions are asked
We can build software to meet this scope?
Is the project feasible?
Software engineers too often rush (or are pushed) past these questions.
Later they become mired in a project that is doomed from the onset.
Feasibility
After the scope is resolved, feasibility is addressed
Software feasibility has four dimensions
Technology: If the project technically feasible, if it within the state of the
art, can defects be reduced to a level matching the application's needs?
Finance: If financially feasible, can development be completed at a cost
that the software organization, its client, or the market can afford.
Time: The project will time-to-market beat the competition.
Resources: Does the software organization have the resources needed to
succeed in doing the project?
Analyze risks
Inaccurate Estimations
Scope Variations
End-user Engagement
Stakeholder Expectations
Poor Quality Code
Poor Productivity
Inadequate Risk Management
Low Stakeholder Engagement
Inadequate Human Resources
Lack of Ownership
Project Resources Resource
Human Resources
Planners need to select the number and the kind of people skills needed to
complete the project
They need to specify the organizational position and job specialty for each
person
Small projects of a few person-months may only need one individual
Large projects spanning many person-months or years require the location of
the person to be specified also
The number of people required can be determined only after an estimate of
the development effort
Reusable Software Resources
Full-experience components
Components are similar to the software that needs to be built
Software team has full experience in the application area of these
components
Modification of components will include relatively low risk
Partial-experience components
Components are related somehow to the software that needs to be built
but will require substantial modification
Software team has only limited experience in the application area of
these components
Modifications that are required have a fair degree of risk
New components
Components must be built from scratch by the software team specifically
for the needs of the current project
Software team has no practical experience in the application area
Development Environment Resources
A software engineering environment (SEE) consolidates hardware, software,
and network resources that provide platforms and tools to develop and test
software work products
Most software organizations have many projects that require access to the
SEE provided by the organization
Planners must identify the time window required for hardware and software
and verify that these resources will be available
Resource:
1. [Link]
development-and-software-engineering-projects
2. [Link]
3. [Link]
4. [Link]