Implementing an Enterprise Content Management requires a sound approach to the Solution Architure. Content is complex and can often include compound information and multiple objects.
Solution Architecture addresses this complexity through a design that takes into account the content lifecycle as it impacts various processing stages relating to its integration with applications and business processes. Our solution architecture design is divided in two distinct section:
- Taking business requirements and transfert it to a System Requirements Specifications (SRS)
- From SRS, create a System Design Document (SDD) that describe and define the blue print of your solutions
SRS
The System Requirements Specifications is a document describing an organization's understanding of a potential client's system requirements and dependencies at a particular point in time, usually prior to any actual design or development work. This ensures that both the client and the organization understand the other's requirements from that perspective at a given point in time.
The SRS document itself states in precise and explicit language those functions and capabilities a software system must provide, as well as states any required constraints by which the system must abide. The SRS also functions as a blueprint for completing a project with as little cost growth as possible. The SRS is often referred to as the "parent" document because all subsequent project management documents, such as design specifications, statements of work, software architecture specifications, testing and validation plans, and documentation plans, are related to it.
It's important to note that an SRS contains functional and nonfunctional requirements only; it generaly doesn't offer design suggestions, possible solutions to technology or business issues, or any other information other than what the development team understands the customer's system requirements to be.
A well-designed, well-written SRS accomplishes four major goals:
- Provides feedback to the customer.
- Serves as an input to the design specification.
- Serves as a product validation check.
- Serves as a reference for testing and validation strategies
SDD
The System Design Document describes a systems's solution software specifications model in a precise, easy-to-understand, and unambiguous manner. This allows to specify not only the structure but also the behavior of the system under development. The solution design is concerned with developing a model of a system to implement the identified requirements from the SRS.
The System Design Document should enable systems developpers to simulate the solution specifications to verify and validate the system and demonstrate its behavior to end-users and other stake-holders at an early stage. It ensures that the solution model conforms to the system requirements. The System Design Document enables to control the scope of the solution to implement by keeping track of the user's system requirements and enables to assess the impact of any requirements changes
The solution design document defines the problem that the finished product is intended to solve and outlines the approach used to reach this solution. It provide a focus for feedback and discussion as the development progresses, provides a common terminology to ensure a clear and concise communications between all te stakeholders. It also provides the initial source material for estimating the work efforts required to develop, design system components tests and developing user documentation.
Please contact us for additional information