When to involve us
We use a formal process for analysing requirements and producing the Project Specification document. The document is explicit enough to clarify and to eliminate most ambiguities and inconsistencies for both the organisation that will use the software and the software developers who will implement it. It is easily understood by business staff and is equally clear for developers. At the heart of the Project Specification and most crucial to it are the Process Definitions.
Each process that is to be targeted for software development requires a key organisational specialist to draft its Process Definition.
The earlier in the creation of each process definition you call us in to work with your experts the quicker you will create workable process definitions. Generally the best time to call us in will depend on the complexity of the process to be defined, the IT skills available within your organisation and the level of your existing IT infrastructure
The finished document for each process consists of at least the process name, the key staff members and their role in the construction of the document, their role in the organisation and the step by step procedure that a computer operator will perform when using the computer. The step by step procedure consists of a flow of steps in the form of 'User enters ...', 'computer displays/prints ... 'etc. We call it the dialogue.
It is far less costly to change and develop a Process Definition than to change program code once it has been written. As such it is the best medium in which to evolve and refine a specification that is easily understood by the business and easily implemented by the developers.
What our involvement is
1 To ensure that each PD is clear and unambiguous for the developers as well as the business staff. If a PD is ambiguous then a fixed price and delivery time for the implementation cannot be calculated.
2 To obtain signed confirmation of each PD by the key staff and specialists in the organisation who are listed in the PD. Without signed confirmation of each PD the implication is that the key staff have either not yet unanimously decided what is wanted or are still in disagreement about what is wanted. This leads directly to wasted time and money spent on rework later on in development.
3 To highlight immediately any requirements that are impossible to deliver, would incur excess development cost or would require excessive hardware and/or software investment by the organisation.
4 To pinpoint any essential hardware and/or software investment that would be needed by the organisation.
Once the PDs have been signed off CCS can offer fixed price/delivery dates for the implementation of each module defined in each PD.
© Clear Computer Solutions Ltd. 2006. All rights reserved.