software engineering i by hmftj

Presentation Members

B-18298 Hafiz Furqan Tahir

B-18108 Abdul Wahab Ahmed B-18108 Muhammad Osama Hanif

Department of Computer Science, University of South-Asia

Software project Management

2

What is software program management?

Definition

Software project management is the process of managing software that is built and implemented as a project, taking into account life-cycle considerations and generally with a wide audience. It is the discipline and business process which governs a project from its inception to the market or customer delivery and service in order to generate biggest possible value to the business

3

Software development process

Aspects of software development

A software development process is concerned primarily with the projection aspect of software development, as opposed to the technical aspect, such as software tools. These processes exist primarily for supporting the management of software development, and are generally skewed toward addressing business concerns. Many software development processes can be run in a similar way to general project management processes

4

Example of software development processes

Requirements management

Requirements management is the process of identifying,eliciting,documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. New or altered computer system Requirements management, which includes Requirements analysis, is an important part of the software engineering process; whereby business analysts or software developers identify the needs or requirements of a client; having identified these requirements they are then in a position to design a solution.

5


Risk management

Risk management is the process of measuring or assessing risk and then developing strategies to manage the risk. In general, the strategies employed include transferring the risk to another party, avoiding the risk, reducing the negative effect of the risk, and accepting some or all of the consequences of a particular risk. Risk management in software project management begins with the business case for starting the project, which includes a cost-benefit analysis as well as a list of fallback options for project failure, called a contingency plan

6


Change management

Change management is the process of identifying, documenting, analyzing, prioritizing and agreeing on changes to scope (project management) and then controlling changes and communicating to relevant stakeholders. Change impact analysis of new or altered scope, which includes Requirements analysis at the change level, is an important part of the software engineering process; whereby business analysts or software developers identify the altered needs or requirements of a client; having identified these requirements they are then in a position to re-design or modify a solution. Theoretically, each change can impact the timeline and budget of a software project, and therefore by definition must include risk-benefit analysis before approval.

7


Software configuration management

Software configuration management is the process of identifying, and documenting the scope itself, which is the software project underway, including all sub-projects and changes and enabling communication of these to relevant stakeholders. In general, the processes employed include version control, naming convention (programming), and software archival agreements.

8


Release management

Release management is the process of identifying, documenting, prioritizing and agreeing on releases of software and then controlling the release schedule and communicating to relevant stakeholders.

Most software projects have access to three software environments to which software can be released; Development, Test, and projection. In very large projects, where distributed teams need to integrate their work before release to users, there will often be more environments for testing, called unit testing, system testing, or integration testing, before release to User acceptance testing (UAT).

Standish Group Report.

02/13/15

All projects need to have a committed executive sponsor or project ownerwho supports the project and takes responsibility for the outcome. Lesson One inthe CHAOS Knowledge Center (CKC) outlines the skills and the responsibilities ofthe executive sponsor. Executive management support is also the first Factorof Success for Small Projects. Our Executive Sponsor Appraisal tests theseskills. Small projects allow a new or inexperienced executive sponsor to gainexpertise while not burdening his or her main job function. Here, the CHAOS 10Success Points for Executive Support are modified for small projects.The nice thing about small projects is they don’t require high-powered executivesponsors—they should be reserved for transformational and large projects. Smallprojects need a skilled and engaged executive, but the executive could be a midlevelmanager—or in the case of agile, a project owner—who is enthusiastic about the success ofthe small project. However, if a high-powered executive sponsor adopts a small project as his or herpet project, all the more power to the team.

10

Project planning, monitoring and control

The purpose of project planning is to identify the scope of the project, estimate the work involved, and create a project schedule. Project planning begins with requirements that define the software to be developed. The project plan is then developed to describe the tasks that will lead to completion.

The purpose of project monitoring and control is to keep the team and management up to date on the project's progress. If the project deviates from the plan, then the project manager can take action to correct the problem. Project monitoring and control involves status meetings to gather status from the team. When changes need to be made, change control is used to keep the projects up to date.

02/13/15

Differences Between Black Box Testing and White Box Testing

Criteria Black Box Testing White Box Testing

Definition

Black Box Testing is a software testing method in

which the internal structure/ design/

implementation of the item being tested is NOT

known to the tester

White Box Testing is a software testing method in

which the internal structure/ design/

implementation of the item being tested is known

to the tester.

02/13/15



Levels Applicable To

Mainly applicable to higher levels of

testing:Acceptance TestingSystem Testing

Mainly applicable to lower levels of testing:Unit

TestingIntegration Testing

Basis for Test CasesRequirement

SpecificationsDetail Design

02/13/15



ResponsibilityGenerally, independent

Software TestersGenerally, Software

Developers

Programming Knowledge Not Required Required

Implementation Knowledge

Not Required Required

14

Conclusions

Project management software industry's future looks especially promising. During the global recession, industrial countries around the world devoted billions in economic stimulus funds for infrastructure and other projects. This has created considerable demand for project management software.

15

References

Article ~ hmftjhttp://www.merl.com/areas/bpm/http://bcalliance-international.com/our-services/risk-managementhttp://blogs.msdn.com/b/willy-peter_schaub/archive/2011/01/13/requirements-management-guidance-where-is-the-feature-work-item-type.aspxhttp://findicons.comhttp://www.turbosquid.com/3d-models/conveyor-belts-max/369307http://techchai.com/2011/07/07/free-project-planning-software-to-improve-your-daily-work/http://iamhash.blogspot.com/2011/06/anatomy-of-success.htmlhttp://en.wikipedia.org/wiki/Software_project_managementThe Future of IT Project Management Software - By Stacy A. Goff Book