0 Bewertungen0% fanden dieses Dokument nützlich (0 Abstimmungen)
15 Ansichten6 Seiten
The document discusses ideal proportions of time for different phases of a systems development project, with a focus on the build phase. It recommends spending the most time on testing at 30-40% of the total project time. Documentation and data migration each should take 10-15% of time, while import/export takes 5-10% of time.
The document discusses ideal proportions of time for different phases of a systems development project, with a focus on the build phase. It recommends spending the most time on testing at 30-40% of the total project time. Documentation and data migration each should take 10-15% of time, while import/export takes 5-10% of time.
The document discusses ideal proportions of time for different phases of a systems development project, with a focus on the build phase. It recommends spending the most time on testing at 30-40% of the total project time. Documentation and data migration each should take 10-15% of time, while import/export takes 5-10% of time.
Ideal proportions of time to be spent on different phases of a systems
Table 12.2 development project, focusing on details of build phase Data migration
• Data migration: Data migration is the transfer of data
from the old system to the new system. When data are added to a database, this is known as populating the database. • Import and export: Data can be ‘exported’ from an old system and then ‘imported’ into a new system. Testing
• Test specification: A detailed description of the tests
that will be performed to check the software works correctly. • Test plan: Plan describing the type and sequence of testing and who will conduct it. The V-model of systems development relating analysis and design Figure 12.1 activities to testing activities Testing (continued) • Developer tests – Module or unit tests. – Integration or module interaction testing – New function testing • End user tests - The purpose of these is twofold: first, to check that the software does what is required; and second, to identify bugs, particularly those that may only be caused by novice users. • Benefits-based testing - test against the business benefits that the system confers. • Test environment - A specially configured environment (hardware,software and office environment) used to test the software before its release. Documentation
Documentation occurs throughout the software
lifecycle, such as when requirements are specified at the analysis stage, but it becomes particularly import-ant at the implementation and maintenance stages of a project.