Development of eCommerce, ERP and custom functionality

Crimsonwing approaches system design and development using a proven, structured approach.

The Key Roles

Solution Architect - Has responsibility for designing and defining a business solution that meets the needs of the client. This takes the initial form of a detailed Functional Requirements document, and will define a business solution that is technically feasible, with associated definition of high level technical tasks and resource estimates. Once the project starts the Solution Architect will be involved in agreeing with the client the detail of any requested changes.

Technical Architect - Will use the Functional Requirements document to create a detailed Technical Specification of the work required to develop the solution. This will be done in close cooperation with the client as work at this level of detail will often identify anomalies or need for more detailed information that needs to be agreed with the client. The technical architect is also responsible for identifying and resolving design issues at any stage in the project, and for producing the program specifications that ensure that requirements are met. The person also reviews technical constraints and discusses complex functions with users and analysts, whilst also addressing the non-functional requirements.

Developer - Is responsible for program design, coding, unit testing, program documentation, assisting in system and user acceptance testing, and in operations hand-over.

Development techniques

The following techniques may be used in developing the system:

• Process modelling - A process is a set of input and output activities, that helps a firm create value for its customers. Process diagrams are graphical representations of all the firm's processes and includes the storage, manipulation and exchange of data between the firm and some external entity and also between the various units of the firm. Process models are considered to provide an alternative to data flow diagrams, which have been around for a long time. In recent times, with the large number of organisations involved in business process reengineering (BPR), process modelling has become increasingly popular.
• Functional decomposition – A technique which decomposes functions, hence demonstrating the hierarchical relationships among the functions and sub-functions. A function hierarchy diagram is a diagram that shows all the functions involved in your system in a hierarchical manner like in an organisational chart. Unlike the process model or the data flow diagram, it does not show the organisational units involved in the functions, the data stores or the data flows. It just specifies the parent function (the function at the very top) and the sub or child functions underneath it. Each child function can also be broken down into further sub functions.
• Entity Relationship modelling - An E-R model or entity-relationship model is a logical representation of the data for a firm or business area. The E-R model consists of entities, relationships between or among entities, and the attributes of the entities. In order to create a detailed and fairly comprehensive E-R model, one has to define clearly its relevant components, such as the entities, attributes, relationships, and the degree and cardinality of a relationship.
• Data Flow Diagrams - A Data Flow Diagram (DFD) is a process-oriented graphical representation of an application system. In the words of Hoffer, George and Valacich (1999), a DFD "is a picture of the movement of data between external entities and the processes and data stores within a system."
• Unified Modelling Language (UML) helps enables the technical designer to specify, visualise, and document models of software systems, including their structure and design, in a way that meets all requirements.
• Use Case Scenarios - The use case scenarios are intended to describe the ways typical usage of web services in real life. These are used by Crimsonwing for load and system testing.
• Facilitated workshops – A technique used in fast-track projects whereby attendees are allowed to gain an overall perspective on the problem/issue at hand. These workshops are thus highly productive, increase ownership of the solution, can accelerate consensus building, and usually result in better quality of decisions.
• Risk management – A key project management technique applied proactively to assess the likelihood and impact of risks and thus enable determination of relative priorities and considerations to prevent, mitigate or deflect the risk.
• MoSCoW prioritisation – A prioritisation technique based on 'fit-for-business-purpose' criteria. Functionality is kept variable whereas time and quality parameters are kept constant. The four priorities used are (in decreasing order of importance):
  • Must have – the minimum usable subset, guaranteed delivery
  • Should have – can work around at great cost to business. The team would work all out to achieve this
  • Could have – can work around but significant benefits. The team would do its best endeavours to achieve this.
  • Would not have – wait until next time. Re-prioritised work which will be done in a subsequent phase / iteration.

Testing Approach

Crimsonwing adopts an integrated testing approach to deliver high-quality systems. Testing is built into each stage of development until the system is accepted by users. During the Technical Analysis and Design Stage – Testing activities include producing the System Architecture Test Model and the Outline Testing Plan. Prototype testing also occurs during this stage.

During the Development Stage – Testing activities include prototype testing, unit testing, low-level integration testing, reviewing unit test results, taking corrective action (if any) and regression testing, preparing the System Test Plan, and preparing the User Acceptance Test Plan. Realistic test data and data volumes are used during this stage to make testing as realistic as possible.

During the System Testing Stage – Testing activities include system testing, reviewing system test results, taking corrective action (if any) and regression testing.

During the Implementation Stage – Testing activities include supporting User Acceptance Testing, taking corrective action (if any) and regression testing.