SEPA5, p.199: “For our purposes, software quality is defined as conformance to explicitly stated functional and performance requirements, explicitly documented development standards, and implicit characteristics that are expected of all professionally developed software.”
Or basic ideas about SW quality based on Pressman.
I considered the following as the main issue; additional information to this was awarded
SEPA5, p. 206
Review, formal technical review, walkthrough, inspection
· The focus of the FTR is on a work product (e.g., a portion of requirements specification, a detailed component design, a source code listing for a component).
· Between three and five people (typically) should be involved in the review.
· Advance preparation should occur but should require no more than two hours of work for each person.
· The duration of the review meeting should be less than two hours.
SEPA5, p. 481:
· Module/unit – a single module/unit, test stubs/drivers, white box techniques
· Integration – connect modules, both black and white box techniques
· Validation – against requirements, black box techniques
· System – outside of software: HW, people, databases, other SW
Comments on how the SQA is done in this project:
· are any reviews conducted
· is the software tested and how
· will you use an outside tester or will you do all by yourself?
SEPA5, p. 225:
“Software Configuration management (SCM) is a set of activities designed to control change, establish relationships among them, defining mechanisms for managing different versions of these work products, controlling the changes imposed, and auditing and reporting the changes made.”
Or basic ideas about SCM based on Pressman.
1. Project plan
2. Requirements document
3. Implementation plan
4. User’s guide
5. Executable, the xls-file (the 5 first items must be these, the 6th is anything reasonable)
6. Test and review – SQA – reports
· What is considered for each change before implementation – necessity, effort, feasibility
· What is done except code changed – other documents & plans updated
· Version numbers in documents and in the executable – when updated
·
Possible
use of version control system, back-up file names & folders
SEPA5, p. 367,
“The architecture is not the operational software. Rather it is a representation that enables a software engineer to
(1) Analyze the effectiveness of the design in meeting its stated requirements,
(2) Consider architectural alternatives at a stage when making design changes is still relative easy, and
(3) Reducing the risk associated with the construction of the software.”
Or basic ideas about SW architecture based on Pressman.
What are the logical components of your software:
· User Interface – input data, select actions/reports
· Reporting – different reports and how they are organized/created
· Data storage
How do you divide your software to different components in MS-Excel:
· Forms: MS Excel 5 or VBA modules
· Macros/code: Macro sheets or VBA modules
· Data storage, reporting, etc.: which (how many) sheets, the names
Or …I have not received any help from other people in developing this implementation plan.
The total time used for the course so far is …hours; … hours for lectures, … hours for quizzes, … hours for exercises, and … hours for the project.
None or...
Last updated 23.12.2002