JSlave Software Development Process
1
Product Conceptualization
1.1
Briefly describe the product in non-technical terms by
describing is purpose, scope, function, and meaning.
1.2
Perform Risk Assessment on marketing, strategic
relations, industry trends, and support problems.
1.3
Artifact is Product Design Candidate (PDC)
2
Requirements Gathering
2.1
Analysis of the
Environment, External Interfaces, and Artifacts of the Business Processes
to develop Use Cases for the proposed system.
2.2
Artifact is Software Requirements Specification (SRS)
3
Architectural Specification
3.1
The team identified the distribution of functional
components on the deployment environment and selects high level technologies for
each node. A preliminary high level
design is considered to deploy over the distributed layout.
3.2
Artifact is High Level Design (HLD) – Contents are a
restatement of the requirements in short bulletized format, conceptual
architecture (technology agnostic view), physical architecture (technology
specific view), Data Model, and security model.
This may include an Activity Diagram and/or a Component Diagram..
4
Development (Alpha, Beta, RC, R)
4.1
The next three phases are repeated until all identified
requirements have been realized and customer accepts product.
4.2
Design
4.2.1
The development team produces a Software Development
Plan (SDP) which shall include a description of their approach to software
construction. This may include a
Class Diagram, flowchart, or bullet list describing the approach.
The plan will cover test and deployment plans stating expected required
test environment and deployement support requirements.
The plan will include the identification of a low level methodology for
managing the consttructionm process (XP, SCRUMM, etc).
4.3
Construction
4.3.1
The development team will use the CVS for source code
management while implementing their design in code.
4.3.2
The artifact will be a beta product and required
documentation.
4.4
Testing
4.4.1
The tests are run in accordance with the test plan
developed in 4.2.1. The tests shall
include a re-run of Unit tests, functional tests, system tests, and acceptance
tests.
4.4.2
Artiufact is a Software Test Report (STR) specifiyng
tests performed and their results.
5
Deployment
5.1
Develop demos, train users, package for release, deliver
marketing collateral.
6
Implementation
6.1
Install, Configures, On Site Acceptance Tests
6.2
Artifact is Install Configuration Report (ICR)