|
As various
components of the application complete the Design phase,
they must be engineered into an actual solution. The solution combines the results from the design phase into a tangible, scalable application. The two deliverables for Develop are:
Functional Specification Approved Milestone
The deliverable is a functional specification. The
functional specification serves as a contract between
all Azavar team members and you. This contract will
be derived from the overall business objectives, user classes
and the activities each user class expects to perform. The
functional specifications will categorize your requirements
into a set of logical user services, business services and
data services.
Functional specifications will clearly define the visual
design, functional interfaces and data requirements of the
application. They will also define the external interfaces,
interoperability, performance goals and other assumptions
and constraints that bind the approach to the proposed solution. The
functional specifications will reflect the consensus and
commitment of all team members, and will drive internal scheduling
and external communication.
Code Complete Milestone
When the functional specification document has been baselined,
the development team will have the primary ownership of the
Code Complete milestone. Again, this will be an iterative
process that may include parallel development and integration
of components from many sources. It is also likely
to include a number of Beta or "pre-release" versions.
All team members will have specific responsibilities as
the overall team moves toward the Release of Product milestone. In
this final phase, Testing/QA will have the primary responsibility
for certifying readiness for release and turning over the
project to Logistics Planning.
The following lead to meeting the functional specification
approved milestone:
- Build Individual Components
Now that all is planned and has been mapped out, it is time
to build the components that will comprise your Web application.
- Assemble Components
Bringing together components and ensuring successful integration
is key to a successful implementation.
- Test
Part of the development process
is implementing a testing procedure. Testing ensures
the site quality based on appearance, compatibility, usability
and performance.
Appearance: addresses the cosmetic issues of the application,
including:
- Text, Title and Link Treatments
- Font Usage
- Table Structures
- Graphic Integrity
- Spelling Errors
Compatibility: checks the appearance and operation
of the application across the target platforms, including:
- Browser Software and Versions
- Operating Systems and Versions
- Hardware Platforms (Mac or PC)
- Hardware Requirements
- Internet Connections
Usability: assesses user interaction with
the application:
- Is the navigation intuitive?
- Is there a clear sense of structure?
- Is the language used clear and concise?
- Are user intentions met with expected system responses?
Performance: gauges the quality and reliability of
system responses through Unit, Assembly and Stress test
scripts. It measures the following:
- Speed
- Accuracy
- Response Time
- System Errors
|
