INITIAL PHASES
In the initial phases of Scoping, Discovery, and Analysis, Robocoder Corporation's solution analysts work closely with business users to define business processes for automation.
After storyboarding and sometimes wire framing, rigorous test cases are developed ahead for the subsequent prototype, so that the system can be designed to satisfy these test cases and consequently meet user requirements. The focus here is to produce implementation-ready software the first time. When clients invest more time up front to get the design right, the implementation phase is incredibly fast - a matter of days and weeks rather than months.
SCOPING
In Scoping, all the elements of the task are identified, such as stakeholders, locations, business performance metrics, business and technical constraints and risks, and so on.
Business requirements, organizational infrastructure, and resources are also determined. From newly defined alternatives, the analysts select a solution. At the end of this phase, deliverables may include:
- Project Description or Charter
- Business Requirements Draft
- Estimate
DISCOVERY
In Discovery, the analysts first divide the job into four components: Workflow, Rules, Data, and Technology.
These will flow through the subsequent Analysis and Design stages. Robocoder staff examine existing systems and data; they begin determining what the rules need to be (rule mining); and they document rules and workflow diagrams. They then move on to the conceptual data model and data quality assessment. Finally, technological requirements are determined and a tiered technology diagram is generated. At the end of this phase, deliverables may include:
- Business Requirements Signed-off
- Conceptual Solution Prepared
- Storyboard Verified
ANALYSIS
This is where the analysts get into the application process flow, solidify rule methodologies, and complete mining, analysis, and optimization of rules.
On Rintagi™ anti-aging App Platform, each business rule can be classified as one of Constraint, Computation, Inference or Action Enabler, and can be managed independently. Validation workshops are held with the business users to make sure the business rules are correct, and then the rules are finalized. Next, analysts complete a data source quality assessment, and determine history and archive requirements. A logical data model is developed and integrated with enterprise data. Entity relationship diagrams are created, data volumes are estimated and conversion specifications are developed. Finally, the analysts identify needed interfaces between technologies and conduct a Proof of Concept. At the end of this phase, deliverables may include:
- Conceptual Solution Signed-off
- Wireframe Verified