1. Software Engineering
College of Arts, Media and Technology ,CMU.
Kittitouch S.
1.1-12-12-11

2. 




Development plan and quality plan objectives
Elements of the development plan
Elements of the quality plan
Development and quality plans for small
projects and for internal projects
Development plan and quality plan in
ISO29110

3. 
Are based on proposal materials that have
been re-examined and thoroughly updated.

Are more comprehensive than the approved
proposal, especially with respect to
schedules, resource estimates, and
development risk evaluations.

4. 
Include additional subjects, absent from the
approved proposal.

Were prepared at the beginning of the
project to sound alerts regarding
 scheduling difficulties
 potential staff shortages
 problems with meeting contractual milestones
 modified development risks

5. 
Development and quality plans are major
elements needed for project compliance
 ISO9000.3
 ISO730
 ISO12207
 ISO29110
 CMMi

6. 1.
Scheduling development activities that will
lead to the successful and timely completion
of the project, and estimating the required
manpower resources and budget.
2.
Recruiting team members and allocating
development resources (according to
activity schedules and manpower resource
requirement estimates).

7. 3.
Resolving development risks.
4.
Implementing required SQA activities.
5.
Providing management with data needed
for project control.

8. 1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Project products, specifying “deliverables”
Project interfaces
Project methodology and development tools
Software development standards and procedures
Map of the development process
Project milestones
Project staff organization
Required development facilities
Development risks and risk management actions
Control methods
Project cost estimates

9. 
The development plan includes the following
products:
 Design documents specifying dates of
completion, indicating those items to be delivered
to the customer (“deliverables”)
 Software products
(specifying completion date and installation site)
 Training tasks
(specifying dates, participants and sites).

10. No.
Deliverables/Release
Media
Qty
Due date
1
Proposal
Hard copy
4
12-12-2011
2
SRS
Hard copy
1
20-12-2011
3
Acceptance test report
Hard copy
1
30-01-2012
4
Software
DVD
10
1-02-2012
Example of Deliverables table

11. 
Project interfaces include:
 Interfaces with existing software packages
(software interface)
 Interfaces with other software and/or hardware
development teams that are working on the same
system or project
(i.e., cooperation and coordination links)
 Interfaces with existing hardware
(hardware interface)

12. 
Software development model
 Waterfall
 Agile
 V-Model and so forth

Development tools
 Hardware and Software
 Management tool

13. 
Software development standards
 ISO
 CMMi
 TQS

Procedures
 Processes
 Tasks
 WBS:Work breakdown structure

14. 
An estimate of the activity’s duration. These
estimates are highly dependent on the
experience gained in previous projects.

The logical sequence in which each activity is
to be performed ,including a description of
each activity’s dependence on previously
completed activities.

15. 
The type of professional resources required
and estimates of how much of these
resources are necessary for each activity.

18. 
For each milestone, its completion time and
project products (documents and code) are to
be defined.

19. The organization plan comprises:
 Organizational structure
 Professional requirements
 Number of team members required for each
period of time
 Names of team leaders and team members.

20. 
Required development facilities include
hardware, software and hardware
development tools, office space, and other
items.
For each facility, the period required for its
use should be indicated on the timetable.

21. 
Development risks are inherent in any
project. To understand their pervasiveness,
and how they can be controlled,

A development risk is “a state or property of a
development task or environment,
which, if ignored, will increase the likelihood
of project failure”

22. 



Technological gaps
Staff shortages
Interdependence of organizational elements
The top 10 major software risk items are
shown in the Appendix to this chapter in
Table 6A.1.

23. 
In order to control project implementation,
the project manager and the department
management apply a series of monitoring
practices when preparing progress reports
and coordinating meetings.

24. 
Project cost estimates are based on proposal
costs estimates.

based on updated human resource estimates,
contracts negotiated with subcontractors
and suppliers, and so forth.

25. 
Development plan review and approval is to
be completed according to the procedures
applied within the organization.

26. 1.
2.
3.
4.
5.
List of quality goals
Review activities
Software tests
Acceptance tests for software externally
developed
Configuration management tools and
procedures

27. 
The term “quality goals” refers to the
developed software system’s substantive
quality requirements.

Quantitative measures are usually preferred
to qualitative measures when choosing
quality

28. 
HDS qualitative requirement
 The HDS should be user friendly
 Related quantitative quality goals
 A new help desk operator should be able to learn
the details of the HDS following a course lasting
less than 8 hours, and to master operation of the
HDS in less than 5 working days.

29. 
The quality plan should provide a complete
listing of all planned review activities:
 design reviews (DRs)
 design inspections
 code inspections

30. 




The scope of the review activity
The type of the review activity
The schedule of review activities (as defined
by its priority and the succeeding activities of
the project process)
The specific procedures to be applied
Who is responsible for carrying out the review
activity?

31. No
Stage
Stage Exit Review
Review Item
1 Preliminary Planning
2 Web site Structure
Study
3 Requirement
Specification
4 Project Planning
5 Design 3 Style Home
Pages
6 Design Next Web
Pages
Responsibility
Preliminary
Planning Doc
Web site Structure
Doc
WSRS Document
PL
WPMP Document
Senior
Manager
CD
3 Style Home
Pages (Picture
Layout)
All Web Pages
PL
PL
CD

32. 
The quality plan should provide a complete
list of planned software tests, with the
following designated for each test:

The unit, integration or the complete system
to be tested
The type of testing activities to be carried
out, including specification of computerized
software tests to be applied


33. 
The planned test schedule (as defined by its
priority and the succeeding activities of the
project process)

The specific procedures to be applied
Who is responsible for carrying out the test.


34. 

A complete list of the acceptance tests
planned for externally developed software
should be provided within the quality plan.
items to be included are..
 (a) purchased software,
 (b) software developed by subcontractors,
 (c) customer-supplied software.

35. Who make changes?
What changes are made?
When are changes made?
Why are changes made?

36. 






Requirements
Changes in funding.
Technology advancements.
Solutions to problems.
Scheduling constraints.
Customer expectations.
Unexpected opportunities for an improved
system.

37. 
The quality plan may be prepared as part of
the development plan or as an independent
document.

Review and approval of the quality plan
should be conducted according to the
organization’s standard procedures for such
plans.

38. The development plan:
 Project products, indicating “deliverables”
 Project benchmarks
 Development risks
 Estimates of project costs
The quality plan:
 Quality goals

39. 
Project plan(+ quality goal) is major element
needed for ISO29110 standard.
 Activities relate to ISO29110 (example)
 The Project Plan for the execution of the
project is developed according to the
Statement of Work and reviewed and
accepted by the Customer. The tasks and
resources necessary to complete the work are
sized and estimated.

40. Example of tasks
Project Management (PM) Process
PM
PM.1.8 Calculate and document the project
Estimated Effort and Cost.
Schedule of the
Project Tasks
Resources
Estimated Effort and
Cost
PM
TL
PM.1.9 Identify and document the risks which
may affect the project.
All elements
previously defined
Identification of
Project Risks
PM
TL
PM.1.10 Document the Version Control Strategy
in the Project Plan.
PM
PM.1.11 Generate the Project Plan integrating
the elements previously identified and
documented.
Version Control
Strategy
Tasks
Estimated Duration
Resources
Composition of Work
Team
Schedule of the
Project Task
Estimated Effort and
Cost
Identification of
Project Risks
Version Control
Strategy
Delivery Instructions
Project Plan
ISO
VSE
Certification Preparation Training

41. 
Chapter 6:Daniel Galin. SOFTWARE QUALITY ASSURANCE From
theory to implementation. Pearson Education Limited,2004.