{"id":46,"date":"2019-03-28T11:21:23","date_gmt":"2019-03-28T15:21:23","guid":{"rendered":"https:\/\/sites.bu.edu\/braude\/?page_id=46"},"modified":"2019-03-28T11:40:41","modified_gmt":"2019-03-28T15:40:41","slug":"met-cs-682-systems-analysis-and-design","status":"publish","type":"page","link":"https:\/\/sites.bu.edu\/braude\/courses\/met-cs-682-systems-analysis-and-design\/","title":{"rendered":"MET CS 682 Systems Analysis and Design"},"content":{"rendered":"

Last updated December 28, 2005: Last few changes often in red font<\/p>\n\n\n\n\n\n\n\n\n
Background of the Instructor <\/strong>changed if this is red<\/td>\nLearning Objectives <\/strong>changed if this is red<\/td>\n<\/tr>\n
Contacting Eric Braude <\/strong>changed if this is red<\/td>\nPlagiarism Warning <\/strong>changed if this is red<\/td>\n<\/tr>\n
Evaluation of Students <\/strong>changed if this is red<\/td>\nPolicies – Miscellaneous<\/strong> changed if this is red<\/td>\n<\/tr>\n
Forums: Past and Present <\/strong>changed if this is red<\/td>\nTextbooks and Materials <\/strong>changed if this is red<\/td>\n<\/tr>\n
Home Page of Eric Braude <\/strong>changed if this is red<\/td>\nTopics, Class Dates & Readings <\/strong>changed if this is red<\/td>\n<\/tr>\n
Homework and Due Dates <\/strong>changed if this is red<\/td>\n <\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n

Description:<\/h2>\n

This course describes object-oriented methods of information systems analysis and design for organizations with data-processing resources.\u00a0 It covers the discovery process for system feasibility, and describes stakeholder analysis and information requirements analysis. The course explains use cases and the manner in which they are applied to requirements analysis.\u00a0 It covers project management, control, and risk analysis.\u00a0 Hardware\/software trade-offs are discussed.\u00a0 The Unified Modeling Language (UML) for describing system designs is defined and described.\u00a0 Database utilization is included in the course, as are software designs with UML models.\u00a0 Data flow and state models are integrated with the design coverage.\u00a0 The course covers implementation management, system-level testing, and system installation. 4cr<\/p>\n

\n

Prerequisite:<\/h2>\n

MET CS 579 or MET CS 669.<\/p>\n

\n

Learning Objectives<\/h2>\n

Learning Goals for CS 682<\/p>\n

    \n
  • Distinguish among types of business systems<\/li>\n
  • Describe a proposed systems analysis project<\/li>\n
  • Examine the issues of working in a team<\/li>\n
  • Distinguish high- from low-level requirements<\/li>\n
  • Examine the goals of good system design<\/li>\n<\/ul>\n

    Course Learning Outcomes for CS 682<\/p>\n

      \n
    • Deal with risks<\/li>\n
    • Develop a project schedule<\/li>\n
    • Write functional and non-functional requirements<\/li>\n
    • Write use cases<\/li>\n
    • Use classes in Object-Orientation<\/li>\n
    • Relate classes to each other<\/li>\n
    • Create sequence and other UML diagrams<\/li>\n
    • Construct system architectures<\/li>\n<\/ul>\n
      \n

      Textbook and Materials<\/h2>\n

      System Analysis and Design Methods by Jeffrey L. Whitten, Lonnie D. Bentley.\u00a0 Publisher: McGraw-Hill\/Irwin;<\/p>\n

      \n

      Evaluation of Students<\/h2>\n

      Absorbing and synthesizing system analysis techniques will be expected of all students.\u00a0 To attain excellence, students will be expected to create original analyses and comparisons.<\/p>\n

      The course grade will be computed from the following<\/p>\n

      Weekly assignments: 45%<\/p>\n

      Weekly quizzes: 20%<\/p>\n

      Final: 35%<\/p>\n

      Students may be given a number of pass\/fail assignments<\/span> throughout the semester.\u00a0 A \u201cPass\u201d grade is required on all of these.\u00a0 A grade of A or A+ may be given for a pass\/fail homework when the student has gone well beyond the requirements of the problem and has performed exceptionally.<\/p>\n

      Late homework<\/span> will not be accepted unless there is a reason why it was impossible<\/em> to perform the work in time given work and emergency conditions.\u00a0 In that case, e-mail the written reason should be attached to the homework, which will be graded on a pass\/fail basis if the reason is accepted by me.<\/p>\n

      \n

      Warning concerning plagiarism<\/h2>\n

      Please cite all references and uses of the work of other.\u00a0 All instances of plagiarism must be reported to the College for action.\u00a0 e-mail, see or call me if you have any doubts about the proper use of others\u2019 material. In any case, clearly acknowledge all sources in the context they are used, including code, of course.\u00a0 See plagiarism policies for examples and a fuller explanation.<\/p>\n

      \n

      Syllabus<\/h2>\n

      9\/8 and 9\/22(note): Introduction and Process<\/p>\n

        \n
      • Types of business systems<\/li>\n
      • Participants in systems analysis<\/li>\n
      • A systems analysis example<\/li>\n
      • Introduction to system process<\/li>\n<\/ul>\n

        Readings: Notes + pages 4 through 29 in the textbook<\/p>\n

        9\/29 and 10\/6: System Project Management<\/p>\n

          \n
        • System development processes<\/li>\n
        • Team interfaces<\/li>\n
        • Team inter-personnel issues<\/li>\n
        • Risk management<\/li>\n
        • Project scheduling<\/li>\n<\/ul>\n

          Readings: Notes + pages 80 through 179 in the textbook<\/p>\n

          10\/13 and 10\/20: System and Requirements Analysis<\/p>\n

            \n
          • The meaning of \u201cRequirements\u201d<\/li>\n
          • High-level requirements<\/li>\n
          • Detailed requirements<\/li>\n
          • Functional requirements<\/li>\n
          • Non-functional requirements<\/li>\n<\/ul>\n

            Readings: Notes + pages 184 through 267 in the textbook<\/p>\n

            10\/27 and 11\/3: Modeling with UML<\/p>\n

              \n
            • Classes<\/li>\n
            • Class relationships<\/li>\n
            • Use cases<\/li>\n
            • Sequence diagrams<\/li>\n
            • Data Flow diagrams<\/li>\n
            • State diagrams<\/li>\n
            • Activity Diagrams<\/li>\n<\/ul>\n

              Readings: Notes + pages 270-289, 342-397, 428-465 in the textbook<\/p>\n

              11\/10 and 11\/17: System Architectures<\/p>\n

                \n
              • Design Purposes<\/li>\n
              • Software Frameworks<\/li>\n
              • Trading off Architecture Alternatives<\/li>\n
              • The Fa\u00e7ade Design pattern<\/li>\n
              • Categorizing system architectures<\/li>\n
              • Component technology<\/li>\n<\/ul>\n

                Readings: Notes + pages 470 through 545 in the textbook<\/p>\n

                12\/1 and 12\/8 Object-Oriented Designs<\/p>\n

                  \n
                • Relating Use Cases, Architecture, and Detailed Design<\/li>\n
                • Sequence and Data Flow Diagrams for Detailed Design<\/li>\n
                • Detailed Data Flow Diagrams<\/li>\n
                • Specifying classes and functions<\/li>\n
                • Standards for Detailed Design<\/li>\n<\/ul>\n

                  Readings: Notes + pages 684 through 716 in the textbook<\/p>\n

                  12\/15: Final<\/p>\n

                  \n

                  Forums — past and present<\/h2>\n

                  Fall 2004<\/p>\n\n\n\n\n
                  Group home page:<\/td>\nhttp:\/\/groups.yahoo.com\/group\/682F04<\/td>\n<\/tr>\n
                  Group email:<\/td>\n682F04@yahoogroups.com<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

                  Last updated December 28, 2005: Last few changes often in red font Background of the Instructor changed if this is red Learning Objectives changed if this is red Contacting Eric Braude changed if this is red Plagiarism Warning changed if this is red Evaluation of Students changed if this is red Policies – Miscellaneous changed […]<\/p>\n","protected":false},"author":2828,"featured_media":0,"parent":22,"menu_order":4,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/pages\/46"}],"collection":[{"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/users\/2828"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/comments?post=46"}],"version-history":[{"count":2,"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/pages\/46\/revisions"}],"predecessor-version":[{"id":48,"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/pages\/46\/revisions\/48"}],"up":[{"embeddable":true,"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/pages\/22"}],"wp:attachment":[{"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/media?parent=46"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}