|
SOFTWARE DEVELOPMENT PROCESS
What is your Software Development process?
We have well-defined processes for software development and maintenance
projects. A handbook exists that defines the software development
process. In addition, we use a CAIRO methodology to clearly define
roles and responsibilities throughout the process.
What Software methodologies do you utilize?
Rational Unified Process (RUP)
Use Case methodology for capturing functional requirements
UML design methodology
Agile methodologies (client-determined)
How are processes and methodologies conveyed to the staff?
Through formal training and periodic audits of performance to processes
What technical design approach do they utilize? How is it documented?
Primarily, UML-based design which is documented using Rational Rose.
Do you write product requirements?
We leverage different methodologies, but prefer iterative processes
to ensure the right requirements are driven out of the process early
and placed appropriately given scope limitations, so that good decisions
are made.
What process/format do you use for product requirements?
Use Cases with accompanying prototype (if deemed necessary)
What are the typical deliverables of your Software Development
Process?
Our typical deliverables include: A) Project Plan, B) Requirements documents
(Use Cases and/or Systems Requirements Spec - SRS), C) Technical Design
Specs (architecture, detailed design of code and databases), D) Test
plans and scripts, E) Commented source code, Executable code, F) Test
results, and G) All Installation documentation.
What is your approach to configuration management? Release management?
Build management?
Our OSDC has a formally documented process for configuration/build/release
management. The process follows the guidelines of CMM and has been
included in the CMM Level 5 certification. The document details
the required and optional steps as well as how to use the CM tool,
PVCS Version Manager.
|
