CAP Embryonic
Bookmark and Share

Systems Analysis & Design

|Overview| |Prototyping| |Modeling| |Feasibility Study| |Documentation| |Process| |Costs|

Overview

We perform a full systems analysis and design of the system you wish to build to ensure that the product you wish to develop is properly thought through before development even starts. Many companies make the mistake to think that this is a waist of time and money. Essentially, not following this route is a waist because it ensures that when a system steps in to the development phase, development time is cut down to a minimum as it does not have to be done over and over because of things that were never considered in the start. In short, writing documentation is faster than writing, debugging and testing code

[Back To Top]
 

Prototyping

This approach often provides a fast way for clients to see what they want the system to do and look like before spending too much money on writing a full-scale system, and then the business case fails. It is a faster an cheaper way to show the client what can be done and is scrapped after the client has decided how to move forward.
  • If the client decides not to move forward with the project because of possible business challenges or limitations identified during this process, the project is scrapped and the analysis phase terminated.
  • If the client however does decide to move forward, the prototype is scrapped, and a functional specification written based on the findings made in the prototyping session, and the development for the actual product initiated


[Back To Top]
 

Modeling

We create graphical models to represent certain use-cases and other scenarios for our clients to view as we find that a graphical representation usually helps clients understand the flow of the system without getting into technical jargon

[Back To Top]
 

Feasibility Study

We also have the ability to do more advanced Systems Analysis and Design by doing a feasibility study of the project you wish to develop.
Feasibility study falls into the following categories
  • Technical Feasibility : This determines if the project you wish to develop is technically feasible. We look at the URS and then do a study around the technical possibilities around it, to determine whether the technical side of the project is possible within budget
  • Economical Feasibility : Here, we look at all the aspects which influences the project and determine whether or not the project will provide a ROI (Return On Investment) or actually run at a loss
  • Operational Feasibility : Will this URS, enable, better or just make the operations of your company worst? We can perform this study on your behalf to determine if the URS will be beneficial or not on an operational level
  • Schedule Feasibility : After laying out so much money, will the business opportunity be met considering the time it will take to develop this requirement, or will it be missed due to timelines being missed? This is what we determine when looking at Schedule Feasibility


[Back To Top]
 

Documentation

Documentation is a critical part of the analysis phase and ensures that everything decided upon is captured in a format that other people can use, which is maintainable. It describes a system in words without trying to understand the code. Documents are written in version control so that everyone can keep track of what was decided on which versions of the document.
We provide the following documents in the Systems Analysis and Design phase but do have the ability to write custom documents based on your company needs:
  • URS (User Requirement Specification) : This is where we provide a template for our clients to fill in. They will then place down their thoughts, return the document back to us, and we begin fact-finding
  • Functional Specification : Once the URS is decided upon, a functional specification is derived from the URS into a more detailed and technical document. This is part of the systems analysis and design phase
  • Technical Specification : Both the top specifications are required by CAP Embryonic, but the technical specification is something the client can decide, whether to move forward with or not. Usually, enough information is captured n the Functional Specification to ensure that the system is written within expectations. The Technical Specification goes into the very low level of software development and is often not needed, but sometimes required depending on how strict the client wants every little detail of the system to be developed according to his/her requirement


[Back To Top]
 

Process

A simple process will look like this:
  • The client will approach us with a requirement
  • We will provide the client with a URS template which needs to be filled in
  • The client returns the completed URS document to us, and we perform fact-finding
  • Once the URS is completed and signed off by both CAP Embryonic and the client, we move into the quoting phase
  • We provide the client with a quote on how much it will cost to write the rest of the documentation for the system and/or development of a protoype. The client is then required to make a 50% payment of the quote given. Once this payment is made and verified, we start with writing the Functional Specification / Prototype within the analysis phase
  • When the Functional Specification / Prototype is completed, both CAP Embryonic and the client will need to sign it off so that we all agree that this is how the system must function
  • We will also write the technical specification if it was required after the functional specification/prototype was developed
  • If a prototype model was pursued, at this stage CAP Embryonic will start writing a Functional Specification based on the prototype if this was required by the client and the prototype was approved, else, move directly to the next step
  • At this stage, the client has to make the final 50% payment based on the quote given. Once this payment is made and verified, the Functional Specification / Prototype will be given to the client to keep
  • Here the client can decide whether to use CAP Embryonic for the development of the system or another company. If the client decides to use CAP Embryonic, we will give 10% discount on the quote given for the development of the system. From here, we move into the Project Management phase

  • Systems Analaysis and Design Process : Image Missing


[Back To Top]
 

Costs

We provide a Systems Analysis and Design service at R350 per hour. Please contact us for further information

[Back To Top]