Page 122 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING

Principles of Software Engineering

Notes • Are software tools used to support the software analysis and design process?
• Are tools used to create software prototypes?

• Are software tools used to support the testing process?
• Are software tools used to support the production and management of documentation?
• Are quality metrics collected for all software projects?

• Are productivity metrics collected for all software projects?
If a majority of the above questions are answered “no”, software process is weak and risk is high.
Technology Risk
Pushing the limits of the technology is challenging and exciting. It is the dream of almost every
technical person, because it forces a practitioner to use his or her skills to the fullest. But it is
also very risky.
Murphy’s Law seems to hold sway in this part of the development universe, making it extremely
difficult to foresee risks, much less plan for them.
The following risk item checklist identifies generic risks associated with the technology to be built:
• Do the customer’s requirements demand the creation of new algorithms or input or output
technology?
• Does the software interface with new or proven hardware?
• Does the software to be built interface with vendor supplied software products that are
unproven?
• Does the software to be built interface with a database system whose function and
performance have not been proven in this application area?
• Is a specialized user interface demanded by product requirements?

• Do requirements for the product demand the creation of program components that are
unlike any previously developed by your organization?
• Do requirements demand the use of new analysis, design, or testing methods?

• Do requirements demand the use of unconventional software development methods such
as formal methods, AI-based approaches, and artificial neural networks?

• Do requirements put excessive performance constraints on the product?
• Is the customer uncertain that the functionality requested is “doable”?
If the answer to any of these questions is “yes” further investigation should be undertaken to
assess risk potential.

5.10 Project Monitoring

Project Monitoring is separate from both project management and construction monitoring,
and can be defined as:
“Protecting the Client’s interests by identifying and advising on the risks associated with acquiring
an interest in a development that is not under the Client’s direct control.”

A monitoring system can be defined as an observation system for the project managers to
verify whether the project activities are happening according to planning and whether means
are used in a correct and efficient manner. The system must supply the project management

116 LOVELY PROFESSIONAL UNIVERSITY