Information Technology Reference
In-Depth Information
Successful static testing of all requirements represents a key step in com-
pleting the Analysis stage before the Design stage is started. Part way through
the requirements static testing, the development team can get the irresistible urge
to start the Design stage with the tested but uncorrected requirements. Know-
ing that 85% of software development defects come from bad requirements, the
CPI project executive defers all Design stage development activities until the
requirements static testing is completed. The static testing emergence of new use
cases -09 and -10 along with their positive impact of reducing the major fi le size
requirements reaffi rms the value of thorough static testing before design work
is begun.
13.4 DESIGN STAGE
With the Analysis stage completed, the Design stage is begun. CPI initiates several
concurrent activities that must dovetail before the design is completed. Here are the
activities initiated by CPI in priority order:
(a) a search for database management software that provides
printing the completion certifi cate forms specifi ed in the the draft
architecture design to support use cases -04 and -06,
master fi le and index fi le size support specifi ed in the draft architec-
ture design, and
general user navigation capabilities in the draft architecture design.
(b) a search for workstation hardware that has the fi le storage capability,
backup capacity, and connectivity specifi ed in the draft architecture de-
sign and runs the chosen database management system.
(c) technology independent logical design of the DCPS functionality (nor-
mally the only priority of the Design stage).
1.
2.
3.
13.4.1 Support Systems Design
The search for database management software is undertaken by a joint team of
senior members from the development team and the test team. With a list of most
promising database management software packages, the team takes the following
repeated evaluation approach until a package is found that meets all of the support
requirements. First, the developers hand build a small fi le of real DSA certifi cates
using the database package. Then, the developers use the database package to write a
certifi cate report program. The developers and testers together use the report program
to align and print the hand-built data onto the blank DSA completion forms. If the
forms cannot be printed correctly, then the database management package is rejected
before the other capabilities are attempted. If the forms can be printed correctly, then
the developers and testers move on to write and test representative menus, data entry
screens, and control screens.
Search WWH ::




Custom Search