Design1

467 views

Published on

Published in: Education, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
467
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
9
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Design1

  1. 1. Guide:Er. Deepinder Kaur Presented By: Sonali Nikhil Pallavi
  2. 2. Computer software, or just software, is a collection of computer programs and related data that provides the instructions for telling a computer what to do and how to do it.Software is a set of programs, procedures, algorithms and its documentation concerned with the operation of a data processing system.
  3. 3. System Development Life Cycle
  4. 4. We are going tostudy about the design phase.
  5. 5. Design elements describe the desired software features in detail These design elements are intended to describe the software in sufficient detail.The focus of this process is to cover the gapbetween understanding the specification and implementing them in the software Design process takes inputs of softwarespecifications and is dedicated to plan for implementation of the software.
  6. 6. Design PhaseStructured StructuredAnalysis design
  7. 7. Structured analysis Structured Analysis (SA) in software engineering and its allied technique, Structured Design (SD), are methods for analyzing and converting business requirements into specifications and ultimately, computer programs, hardware configurations and related manual procedures.
  8. 8. Scenario basedBehavioral Analysis model Flow oriented based Class based
  9. 9. To describe customerrequirementTo establish basis ofdesign
  10. 10.  A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system, modeling its process aspects. A DFD shows what kinds of information will be input to and output from the system, where the data will come from and go to, and where the data will be stored.
  11. 11. Synchronous Asynchronous operations operations If data goes to aIf data is going from 1 data store then to bubble to another other bubble
  12. 12. Level 0 P 0 Balancing DFD’s P1Level 1 0.1 P11 P12Level 2 0.1.1 0.1.2
  13. 13.  Also known as “high – level design” Software architecture is made with the help of structured charts
  14. 14. Characteristics of Software DesignCorrectnessUnderstandabilityEfficiencyMaintainability
  15. 15. Process OutcomeIdentify nature of Requirement requirement. specification Analysis & build Functional modal specification system Mismatch b/w Validate solution modal & design are removed Refine design solution Design blueprint Implement design Software solution architecture
  16. 16. cohesion abstraction coupling Concepts Problemmodularity partitioning of design & hierarchy
  17. 17. ModularityConcept of keepingseparate the variousunrevealed aspects Aof a system so thateach aspect can bestudied in isolation. B C
  18. 18. It helps in system debugging.In system repairs.In system building.
  19. 19. Condition must for modularity!!Each module needsto support a well-defined abstraction &have a clear interfacethrough which it caninteract with othermodules.
  20. 20. DecompositionIs creating lower level elements from higher lever key element on the basis of functions & features. Result of this is called MODULES.
  21. 21.  Abstraction of a component describes the external behaviour of that component without bothering with the internal details that produce the behaviour It is essential for problem partitioning.
  22. 22. Functional Dataabstraction abstraction
  23. 23. • Is the basis of partitioning in the functional oriented approach1. • when problem is being partitioned ,the complete transformation function for the system is partitioned into2. smaller functions • The decomposition of the system is in terms of functional modules3.
  24. 24.  It supports certain operations required from a data object, depending on the object & environment in which it is used. Only such operations are visible & internals are hidden. It forms the basis of object oriented design.
  25. 25. Rule of “Divide & Conquer”.Goal is to divide the problem into manageable small pieces that can be solved separately The cost of solving the entire problem is more than the sum of the cost of solving all the pieces Different pieces have to cooperate & communicate to solve larger problem The design produced by using problem partitioning can be represented as a hierarchy of components
  26. 26. Hierarchical structure makes it much easier to comprehend larger problemsAll design methodologies aim to produce a design that employs hierarchical structures
  27. 27.  Fan-in refers to no. of units that use a particular software unit. Fan-out refers to no. of units used by particular software unit
  28. 28. Fan-in for B is 1 & fan- Super-ordinate of B & C out is 2 A Sub-ordinate of A & super-ordinate of D,E&F B CSub-ordinate of B &C D E F
  29. 29.  Two modules are considered independent if one can function completely without the presence of other. The more connections between the modules ,the more they are dependent. Hence, fewer & simpler the connections between modules the easier is to understand them.
  30. 30.  Coupling is the strength of A B interconnections between Highly modules. coupled Highly – coupled modules D C are joined by strong interconnections. A B While loosely-coupled Loosely modules have weak connections. D C Independent modules have no interconnections. A Uncoupled B
  31. 31.  Coupling increases the complexity. To minimize coupling , the no. of interfaces per module. Interface is used to pass information to & from modules.
  32. 32. Reference made from 1 module to anotherAmount of data passed from 1 module to anotherAmount of control passed from 1 module to another
  33. 33.  It represents how tightly bound the internal elements of the module are to 1 another. It gives an idea whether the different elements of a module belong together in the same module. Greater the cohesion of each module in the system , lower the coupling between modules is.
  34. 34. Co-incidental logical temporal proceduralcommunicational sequential functional
  35. 35. Component level design Interface design Architectural design Data/class design
  36. 36.  Known as structural decomposition: actually a conversion of Data flow Diagram to Structured chart
  37. 37.  Selection: determined by “diamond”. This means condition will checked & depending on these modules will be executed. Process Process Process
  38. 38.  Using “semi-circular arrow we represent this. This arrow includes a link to a module implying that module is executed multiple times A B C D
  39. 39. Module AInvocation arrowParameters
  40. 40. Input module: obtain info. From subordinate &passes to super-ordinate Input module
  41. 41. Output module : takes info. From their super-ordinate & pass to sub-ordinate. Output module
  42. 42. Transform module : that transform data into other form.Transform module
  43. 43. Co-ordinate module: manages info. To & from other sub-ordinates. Co-ordinate module A B
  44. 44. Composite module: perform function of more than 1module. Composite moduleB C
  45. 45. Transformation of DFD to structured design.Identify system Identify input Identify output processing transform transform transform
  46. 46. Main A,n sum A,n a A,nreadnums Sort Add_n X,y X,y switch
  47. 47. Any questions
  48. 48. Thankyou you Made By : Sonali Narang B.Ca

×