Managing software development

Managing
Software
Development
Object Oriented
Software Engineering
RespaPeter
Roll No:12
ASIET Kalady

Managing SoftwareDevelopment
ASIET Kalady
ManagingSoftware Development
 Management activities focus on planning the project, monitoring its status,
tracking changes, and coordinating resources such that a high quality
product is delivered on time and within budget.
 Management activities not only involve managers, but also most of the other
project participants as well.
 The main Management activities include
 Communication
 Rationale management
 Software Configuration Management
 Project Management
 Software Life Cycle
Communication
o Communication is the most critical and time consuming activity in
software engineering
o Misunderstandings and omissions often lead to faults and delays that are
expensive to correct later in the development
o Communication includes the exchange of models and documents about the
system and its application domains, reporting the status of work products,
providing feedback on the quality of work products, raising and
negotiating issues, and communicating decisions.
o To deal with communication issues, project participants have many tools
available.
o The most effective one is conventions: when participants agree on
notations for representing information, on tools for manipulating
information, and on procedures for raising and resolving issues, they
already have eliminated substantial sources of misunderstanding.

ASIET Kalady
o Examples of notations include UML diagrams, templates for writing
documents and meeting minutes, and identification schemes for naming
software components.
o Examples of tools include CASE (Computer Aided Software Engineering)
tools for maintaining models, word processors for generating documents,
ad interchange formats for publishing information.
o Examples of procedures include meeting procedures for organizing,
conducting, and capturing a meeting, review procedures for reviewing
documents and providing feedback, and inspection procedures for
detecting defects in model or source code.
o The selected conventions do not need to be the best available; they only
need to be shared and agreed on by everybody.
Rationale Management
o Rationale is the justification of decisions, its rationale includes the
problem that it addresses, the alternatives, the debate developers
considered used to evaluate the alternatives, the debate developers went
through to achieve consensus, and the decisions.
o This is a detailed summary of research on design rationale providing
researchers in software engineering with an excellent overview of the
subject.
o Rationale is the most important information developers need when
changing the system.
o If a criterion changes, developers can reevaluate all decisions that depend
on this criterion.
o If a new alternative becomes available, it can be compared all other
alternative that were already evaluated.
o If a decision is questioned, they can recover its rationale to justify it.

ASIET Kalady
o Unfortunately, rationale is also the most complex information developers
deal with during development, and thus, the most difficult to update and
maintain.
o To deal with this challenge, developers capture rationale during meetings
and on line discussions, represents rationale with issue models, and
access rationale during changes.
Software Configuration Management
o Software configuration management is the process that monitors and controls
changes in work products.
o Change pervades software development.
o Changes include requirement changes, hardware/software platform changes,
and system changes.
o Software configuration management used to be in the realm of maintenance,
when improvements are incrementally introduced in the system.
o Configuration management enables developers to track changes.
o The system is represented as a number of configuration items that are
independently revised.
o For each configuration items, its evaluation is tracked as a series of versions.
o Selecting versions enables developers to role back to a well defined state of
the system when a change fails.
o Configuration management also enables developers to control change.
o After a baseline has been defined, any change needs to assessed and
approved before being implemented.
o This enables management to ensure that the system is evolving according to
project goals and that the number of problems introduced into the system is
limited.

ASIET Kalady
Project Management
o Software project management is the art and science of planning and leading software
projects.
o Project Management activities include: determining the scope of the project, project
planning, implementation of project components in a timely manner, review of project
activities, and a listing of lessons learned during the project.
o A Software Project Management Plan (SPMP) can be used to outline the structure of the
project and how it will be managed.
o Project management does not produce any artifact of its own.
o It includes the oversight activities that ensure the delivery of a high-quality system on
time and within budget.
o This include planning and budgeting the project during negotiations with the client,
hiring developers and organizing them into teams, monitoring the status of project and
intervening when deviations occur.
Software Life Cycle
o System LifeCycle is a process focusedon the activities directly related to production of
the software, forexample, design, coding, and testing.
o General model of the development process is called software lifecycle.
o Software life cycle model represents all the activities and work products
necessary to develop a software system.
o It enables managers and developers to deal with the complexity of the
process of developing software.
o Focusing only on what is relevant to specific issues; developers can more
effectively resolve issues and answer questions.
o The process of developing software can also viewed as a complex system
with inputs, outputs, activities, and resources.
o Same modeling techniques applied to software artifacts are used for
modeling software processes.
o Like software system, software life cycle can be described by several

ASIET Kalady
different models.
o Activity centered: software life cycle models those are focused on the
activities of software development and represented them explicitly as
class object. This view leads participants to focus on how work products
are created.
o Entity centered: this view of software life cycle focus on the work product
created by the activities.
o It leads the participants to focus on the content and structure of the work
product.
Testing
 Testing is the process of finding difference between the expected behaviors
specified by the system models and observed behavior of the implemented
system.
 Unit testing: find difference between the object model design and the
corresponding component.
 Structural testing: find differences between the system design model and a
subset of integrated subsystems.
 Functional testing: finds difference between the use case model and the
system.
 Performance testing: finds difference between nonfunctional requirements
and actual system performance.
 From a modeling point of view, testing is the attempt to show that the
implementation of the system is inconsistent with the system models.
 The goal of the testing is to design tests that exercise defects in the system
and to reveal problems.
 Consequently, testing is usually accomplished by developers that were not

ASIET Kalady
involved with the construction of the system.
 Testing is defined as the systematic attempt to find faults in a planned way
in the implemented software.

Managing software development

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (7)

Similar to Managing software development

Similar to Managing software development (20)

More from Respa Peter

More from Respa Peter (14)

Recently uploaded

Recently uploaded (20)

Managing software development