Please enable JavaScript.

Coggle requires JavaScript to display documents.

Software design - Coggle Diagram

- - - - The tricky problem for the developers is to truncate this learning process at just the right point so that a suitable product can be delivered in a reasonable time and at an affordable cost.
  - - - Focus on the high-level issues until you know enough to produce the overall conceptual design
      - Complete and document the conceptual design.
      - 3.Now make and document your development plan.
      - 4.Once you have the conceptual design, your data gathering process changes. An immediate objective is to test the conceptual design
      - 5.Once you have satisfied yourself that the conceptual design is solid, you can begin to focus on details.
- - - - The following basic design information is the sole re- sponsibility of the software designers
        
        A picture of where the program fits into the system
        
        A logical picture of the program itself
        
        A list of all related objects: scope, class structure, functions provided, where initialized, where destructed
        
        A list of all external variables: includes scope, limits, constraints, where declared, where initialized
        
        A precise description of all external calls and references
        
        A clear statement of the program's logic (pseudocode)
  - - - Briefly, the design phases required are as follows:
        
        1.Define the need (requirements definition).
        
        Define the solution (the system specification).
        
        Conceptualize the solution (the system high-level design).
        
        Divide up the work (the product specifications).
        
        Define the product design (product high-level design).
        
        Define the component design (component high-level design).
        
        Break the products into components (the component specifications).
        
        Break the components into modules (module specifications).
        
        Detail the solution (module detailed design).
        
        Implement the solution (module implementation and test).
- - - - Internal-static: contains a static picture of the object, such as its logical design
      - Internal-dynamic: the object's dynamic characteristics concerning its behaviorThe dynamic behavior of an object can often be described by treating itas a state machine. Other important dynamic characteristics are response times and interrupt behavior.
      - External-static: the static relationship of this object to other objects. An example would be the inheritance hierarchy.
      - External-dynamic: the interactions of this object with other entities
- - - - As you are determining which design methods and representations to use, consider the following:
        
        Use your PSP to establish a productivity baseline for the design methods you currently use.
        
        Measure your design work on a number of projects. Gather enough data to identify how many design defects you inject and the defect types that cause you the most trouble.
        
        Measure your performance with the new design method. Recognize that your productivity and quality will initially decline, so measure several projects.
        
        Analyze these data to see where and how the new method helps or hurts