JSD - Jackson system development
Jackson System Development (JSD) is a linear method of system development created by Michael A. Jackson and John Cameron in the 1980s. It comprises the whole software life cycle directly or providing a framework for more specialized techniques.
The main principles of JSD's work are:
- JSD method lets describe and model the real world, not specifies and not structures the function performed by the system.
- The time-ordered world must be time-ordered itself, JSD depicts the progress in the real world that models it.
- The implementation of the system is based on transformation of specification into efficient set of processes.
Jackson System Development includes three main stages, each of those is divided into steps and sub-steps:
- Modelling stage (analysis) - includes the entity/action step and entity structures step; on this stage is created a set of Entity Structure Diagrams (ESDs) and are identified the entities in the system, the actions, and the attributes of the actions and entities.
- Network stage (design) - contains the initial model step, function step, and system timing step; on this stage is developed a System Specification Diagram (SSD) or a Network Diagram which use rectangles to depict the processes and diamonds to represent their relationships. This stage defines the simulation of a real world, adds the executable operations and processes, and provides the synchronization among processes and introduces the constraints.
- Implementation stage (realization) consists of the implementation step which converts an abstract network model into a physical system and represents it as a System Implementation Diagram (SID).
When implementing the Jackson System Development method and designing JSD diagrams, you can succesfully use the powerful and helpful tools of ConceptDraw DIAGRAM software extended with Entity-Relationship Diagram (ERD) solution from the Software Development area of ConceptDraw Solution Park.
Example 1. JSD in ConceptDraw DIAGRAM software
Entity-Relationship Diagram (ERD) solution offers a lot of predesigned examples, samples and templates, and 2 libraries:
- ERD Chen's Notation library
- ERD Crow’s Foot Notation library
with numerous collection of ready-to-use vector objects for designing diagrams in minutes.
Example 2. Jackson system development - JSD
This sample was created in ConceptDraw DIAGRAM diagramming and vector drawing software using the Entity-Relationship Diagram (ERD) solution from the Software Development area of ConceptDraw Solution Park and shows the Jackson system development (JSD).
Use the predesigned objects, templates and samples of the Entity-Relationship Diagram (ERD) solution for ConceptDraw DIAGRAM to create your own professional ERD and JSD diagrams quick and easy.
All source documents are vector graphic documents. They are available for reviewing, modifying, or converting to a variety of formats (PDF file, MS PowerPoint, MS Visio, and many other graphic formats) from the ConceptDraw STORE. The Entity-Relationship Diagram (ERD) Solution is available for all ConceptDraw DIAGRAM or later users.
NINE RELATED HOW TO's:
You need to draw the Circular Arrows Diagram, Segmented Diagram or Circular Flow Diagram? Any of these diagrams can be fast and easy designed in ConceptDraw DIAGRAM software, which offers the Business Diagrams Solution from the Management Area with extensive drawing tools, predesigned samples and circular flow diagram template. The use of ready template is the easiest way of drawing.
Picture: Circular Flow Diagram Template
ConceptDraw DIAGRAM diagramming and vector drawing software extended with Fishbone Diagrams solution is a perfect tool for software designers and software developers. If you need to create Cause and Effect diagram, Fishbone diagram, Ishikawa diagram from templates and examples, or using the predesigned elements, ConceptDraw DIAGRAM can do this easily.
ConceptDraw DIAGRAM software gives ability to design Fishbone diagrams that identify many possible causes for an effect for problem. Each Fishbone diagram design element included to Fishbone Diagrams library is vector and ready-to-use.
Picture: Fishbone Diagram Design Element
Both Crow’s Foot and Chen’s notations are used to build database models. Each of them has its’ own features, and if you use a proper entity relationship diagram software, you’ll be able to create diagrams of any notation. Database model with clearly defined entities and relationships between them facilitates further work greatly.
This ERD represents the model of Employee Certification Entity. The entity-relationship diagram is a visual instrument of database software development. It is used to structure data and to define the relationships between structured data groups. This ERD was designed with a help of ConceptDraw Entity-Relationship Diagram (ERD) solution. The solution supports the both basic ERD notations used to describe the structure of database: Chen's and Crow’s Foot notations.
Picture: Entity Relationship Software
ERD drawing becomes easier with predesigned entity relationship symbols, work flow shapes, entity relationship stencils. All variety of ERD symbols you may need for ERDs design is packed into libraries and templates from Entity-Relationship Diagram (ERD) Solution for ConceptDraw DIAGRAM diagramming and vector drawing software.
But anyone have an ERD symbols quick reference? Detailed reference information for them is represented at the tables.
Picture: Anyone Have an ERD Symbols Quick Reference?
This sample was created in ConceptDraw DIAGRAM diagramming and vector drawing software using the Flowcharts solution from the Diagrams area of ConceptDraw Solution Park.
This sample shows the Flowchart of the Credit Card Order Process. On this diagram are used the flowchart symbols that represents the processes and documents. The flowchart symbols are connected with arrows.
Picture: Credit Card Order Process Flowchart. Flowchart Examples
When it comes to system construction, a class diagram is the most widely used diagram. UML Class Diagrams is a type of static structure diagram that is used for general conceptual modeling of the systematics of the application. Such a diagram would illustrate the object-oriented view of a system. The object orientation of a system is indicated by a class diagram. It describes the structure of a system by showing the general issues,classes of a system, attributes, operations, interfaces, inheritance, and the relationships between them.
Picture: UML Class Diagram Notation