Scientific Digital will partner with your business to ensure costs are reduced and productivity is increased. Our iterative methodology provides organizations with consistent delivery and ensures employees are engaged and communicated to throughout the lifecycle of business change. Our iterative cycle begins at "Business Needs Analysis" and ends at "Evaluate" before the next iteration begins. Our roadmap, including documentation and requirements management at each step, looks
like this:

• Business Needs Analysis Phase
• Design Phase


• Development, Build and Configure Phase
• Test Phase


• Train and Deploy Phase
  

Our process begins with a Business Needs Analysis phase to understand the scope of the business requirements and objectives of the organization. During the analysis phase we take the time to understand and accurately represent the stakeholders’ needs. We lead and coordinate the collection and verification of customer and business needs; we, also, document and organize the functional and non-functional requirements for the system in order to allow for their successful communication to the entire team.

The analysis phase is mainly an investigational task focused on “what” should be built. The goal is to understand the problem and begin to develop a visual model of what you are trying to build independent of implementation and technology concerns and constraints. The analysis phase provides a conceptual model derived from the analysis of the business requirements.

During this phase, we with work with your Business Staff, Information Technology Staff and Business Partners to develop the conceptual model.

The design phase is composed of tasks focused on “how” the system should be built. The goal of design is to refine the model with the intention of developing a design model that allows for the seamless transition to the next phase, implementation and development. The design phase produces a logical model that can be morphed through the implementation phase in order to produce the physical solution that will be your system.

Typically, the design phase provides the following articles over multiple iterations:

• Business Model
• Formal Business Requirements to Functional Requirements Mapping
• Use Cases
• Class and Sequence Diagrams
• Database Entity-Relationship Diagrams
  

The goal of this phase is to take the logical model that is produced during the design phase and actually implement the system. During this phase the components that make up the system are put together allowing us to shift from programming software, which is writing one line of code at a time, to composing software, where pre-built components are put together to produce a solution that is greater then the sum of the parts.

Given the fact that we are employing an iterative software engineering process, the integration of these components is not a gargantuan task that is handled at the end of software development process. Instead, as smaller elements are produced throughout the lifecycle of the project, they are integrated one by one limiting the length, uncertainty and difficulty of the integration steps.

Moreover, producing component-based architectures facilitate and encourage reuse, which leads to reduced development time and cost and allow for superior quality since each module, package, or subsystem is thoroughly tested throughout the length of the Development phase.