Contents


    Project Iteration 4 -- Move from analysis to system design.

      Process


      1. Review all documentation so far prepared.
      2. Review my web pages about DFDs, Data models, and costs....
      3. Correct any defects I marked in your artifacts.
      4. Describe the required data base.
      5. Validate your DFD against your data base. First every data store in the DFD should also be an entity in your ERD. You may need to change the names of data stores. Then check that every process in your DFD can get the data it needs from entities in your ERD. Also that it can create, update, and delete the data it needs to change.
      6. Revise data base and or DFD.
      7. Resubmit a copy of the whole revised package.

      Note: If a document is not changed, still hand it in for grading. This is my last real chance to spot and remove errors.

      Deliverables.

      Give me a copy of the following:
      1. Name of project and names of team members.
      2. Description and Justification (text, tables, context DFD)
      3. New system (level 0 DFD)
        • Name Sources, sinks, stores, and processes plus data flows!
        • Must follow DFD rules.
        • Must not be a flowchart or activity diagram.
      4. Describe the data in the system as a data base: ERD+attributes. The model should be in third normal form.
      5. Propose a strategy and justify it:
        1. For each process in new system do you
          1. Reuse the current process.
          2. Outsource the whole implementation process to another enterprise who does it for you.
          3. Buy off the shelf solution (which? how much?).
          4. Buy and customize an Off-the-shelf component.
          5. Download and customize an open-source component.
          6. Creatively use existing productivity tools (eg. MS Office).
          7. Embed it into the data base.
          8. Modify existing software (in-house).
          9. Develop it in-house as new software.
          10. Outsource the construction of of parts and glue the result together in-house.
          11. ...

        2. How much does each one cost?

      6. NO flowcharts or activity diagrams.
      7. High level (Business) functional requirements. What must the system do? List at least the names of some important (too the enterprise) use cases.
      8. List any quality requirements. How well must the solution do its work?

      Dead line

    1. Verbal Progress report: start of next class.
    2. Paper work at Start of Next week's class.

    Abbreviations

  1. TBA::="To Be Announced".
  2. TBD::="To Be Done".

    Links

    Notes -- Analysis [ a1.html ] [ a2.html ] [ a3.html ] [ a4.html ] [ a5.html ] -- Choices [ c1.html ] [ c2.html ] [ c3.html ] -- Data [ d1.html ] [ d2.html ] [ d3.html ] [ d4.html ] -- Rules [ r1.html ] [ r2.html ] [ r3.html ]

    Projects [ project1.html ] [ project2.html ] [ project3.html ] [ project4.html ] [ project5.html ] [ projects.html ]

    Field Trips [ F1.html ] [ F2.html ] [ F3.html ]

    [ about.html ] [ index.html ] [ schedule.html ] [ syllabus.html ] [ readings.html ] [ review.html ] [ glossary.html ] [ contact.html ] [ grading/ ]

End