{"id":43,"date":"2019-03-28T11:20:17","date_gmt":"2019-03-28T15:20:17","guid":{"rendered":"https:\/\/sites.bu.edu\/braude\/?page_id=43"},"modified":"2019-03-28T11:40:41","modified_gmt":"2019-03-28T15:40:41","slug":"met-cs-673-software-engineering","status":"publish","type":"page","link":"https:\/\/sites.bu.edu\/braude\/courses\/met-cs-673-software-engineering\/","title":{"rendered":"MET CS 673 Software Engineering"},"content":{"rendered":"

Last updated: October 28, 2005<\/em>. <\/em>The most recent updates are usually in red type<\/em><\/p>\n

Description:<\/strong> Techniques for the construction of reliable, efficient and cost-effective software.\u00a0 Requirements analysis, software design, programming methodologies, testing procedures, software development tools and management issues.\u00a0 Students design and implement a system in a group project.\u00a0 Laboratory course.<\/p>\n\n\n\n\n\n\n\n\n\n
Background of the Instructor red if changed<\/td>\nMidterm Description red if changed<\/td>\n<\/tr>\n
Evaluation of Students red if changed<\/td>\nPlagiarism red if changed<\/td>\n<\/tr>\n
Forums — past and present red if changed<\/td>\nPolicies in Eric Braude\u2019s classes red if <\/em>changed<\/td>\n<\/tr>\n
Home page for Eric Braude<\/td>\nProject and Presentation red if changed<\/td>\n<\/tr>\n
Homework and due dates red if changed<\/td>\nTools red if changed<\/td>\n<\/tr>\n
How to Contact Eric Braude red if changed<\/td>\nTextbooks and Materials red if changed<\/td>\n<\/tr>\n
Learning Objectives red if changed<\/td>\nTopics and Class Dates red if changed<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
    \n
  • Meeting Time:<\/strong> Thursdays 6:00-9:00 pm<\/li>\n
  • Meeting Place:<\/strong> Charles River Campus FLR 121 (Fuller building, opposite the BU Bridge)<\/li>\n
  • Prerequisites:<\/strong> Course in Data Structures and at least one 500-level programming course<\/li>\n<\/ul>\n
    Learning Objectives<\/strong><\/p>\n

    Students will be able to plan software application projects, gather requirements, create an architecture, create a design, implement the code and test the product.<\/p>\n

    \n

    Textbook and Materials<\/h3>\n

    Required<\/p>\n

      \n
    • Optional: Software Engineering: an Object-Oriented Perspective <\/em>by E. Braude (Wiley 2001)<\/li>\n
    • Updated notes<\/li>\n
    • The site for the above book contains a soft version of the case study that you may use for templates, as well as the full case study source code, and the slides for all classes.\u00a0 The latter correspond to the figures in the book.<\/li>\n<\/ul>\n
      A good references (not required):<\/address>\n

      Software Engineering: A Practitioner’s Approach <\/em>by R. Pressman (McGraw Hill)<\/p>\n

      Additional References:<\/p>\n

      The Mythical Man-Month 20th anniversary edition <\/em>by F. Brooks et al<\/p>\n

      A Discipline for Software Engineering<\/em> by W. Humphries (“the PSP book”)<\/p>\n

      Introduction to the Team Software Process<\/em> by W. Humphries (“the TSP book”)<\/p>\n

      \n

      Project Structure<\/h3>\n

      To reinforce a central concept in software engineering, students will work in teams on most project parts.\u00a0 Team leadership will change once during the semester.\u00a0 Specialization within groups may be permitted, but all members must know all parts.\u00a0 Teams will give presentations on the last day of class, and may be called upon to give in-progress reviews.<\/p>\n

      Presentation format for last class<\/h4>\n

      The format of the presentation should be as follows.<\/p>\n

      3 minutes approximately: Introduce members and describe what the application is supposed to do<\/p>\n

      3 minutes approx: Show your design<\/p>\n

      4 minutes approx: Give a demonstration if possible<\/p>\n

      5 minutes: What did **not** work in the process<\/p>\n

      5 minutes: What **worked well** in the process<\/p>\n

      Use different people or pairs to present different parts.\u00a0 Have all set up in advance so that there is no waiting between presenters.<\/p>\n

      \n

      Midterm<\/h3>\n

      The midterm will probably be in the following form.<\/p>\n

      1.\u00a0\u00a0 Describe a realistic process for developing a software application given the following circumstances \u2026…\u00a0 Explain your choice and show a rough schedule.<\/p>\n

      Criteria:\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 a. Adequacy and appropriateness of the process <\/em><\/p>\n

      (A = entirely appropriate number and type of phases)<\/em><\/p>\n

      b. Clarity of description \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0(A = all expressed very clearly, with specifics)<\/em><\/p>\n

      2.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Within the constraints mentioned in question 1, give parts of requirements documentation for the following application.\u00a0 Provide the most important headings for your documentation, as well as illustrative examples<\/em> of content only.\u00a0 Omit “documents referenced”, interface specifications of all kinds, design constraints and “scope”.<\/p>\n

      Your customer is \u2026\u2026.<\/p>\n

      Criteria:\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 a. Clarity of requirements description (A = very clearly expressed examples) <\/em><\/p>\n

      b. Completeness within the (sub) headings you have chosen (A = complete within the subheading; no redundancy) <\/em><\/p>\n

      3.\u00a0\u00a0 Give an overall architecture of the software application described in question 2.\u00a0 Preferably, use two to four annotated diagrams.\u00a0 Accommodate expansion of the requirements; explain.<\/p>\n

      Criteria: \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 a. Clarity of design <\/em><\/p>\n

      (A = very modular and very clear design; low coupling; high cohesion) <\/em><\/p>\n

      b.\u00a0 Growth<\/em> potential of the design i.e. attention paid to reasonable future growth\u00a0 \u00a0\u00a0\u00a0 (A = all key areas and reasonable growth addressed). <\/em><\/p>\n

      \n

      Evaluation of Students<\/h3>\n

      There will be a midterm, together with assignments, given on most weeks for the first two thirds of the semester. The assignments will consist of group work on the term project.<\/p>\n\n\n\n\n\n
      <\/td>\nweight<\/strong><\/td>\n<\/tr>\n
      Midterm <\/em><\/strong><\/td>\n35%<\/td>\n<\/tr>\n
      Project <\/em><\/strong><\/td>\n65%<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Parts of assignments are evaluated equally unless otherwise stated.<\/p>\n

      All members of the group will receive the same grade for each joint submission, factored by peer evaluations within the group.\u00a0 To fulfill your peer evaluation option, you must individually send me an e-mail, after the group’s final submission is made, apportioning your evaluation of the RELATIVE CONTRIBUTION TO THE GROUP’s GRADE as follows. Be fair and rational. Suppose that your group has n participants. Apportion 10(n-1) points among the team members excluding yourself. For example, members of a team consisting of A, B, C, and D, could be evaluated by member B as A=8, C=12, and D=10. The extent of this factoring will be decided by the instructor near the end of the course. Groups have the option to decline peer evaluations, in which case all participants will receive the same grade for each joint submission.<\/p>\n

      Within each project, grades will be apportioned as follows.<\/p>\n\n\n\n\n
      Final submission<\/strong><\/td>\n30%<\/td>\nInfluenced by peer evaluations, if any<\/td>\n<\/tr>\n
      Remainder<\/strong><\/td>\n70%<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Late homework is not accepted unless there is a reason why it was impossible to perform the work. In that case, the written reason should be attached to the homework, which will be graded on a pass\/fail basis.<\/p>\n

      Please also read detailed information about grade averaging method.<\/strong><\/p>\n

      Plagiarism<\/strong> <\/strong><\/p>\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 See plagiarism policy and reference.<\/p>\n

      Syllabus<\/strong><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
      Dt<\/span><\/strong>.<\/span><\/strong><\/td>\nCls<\/span><\/strong><\/td>\nTopic<\/span><\/strong><\/td>\nApproximate project schedule<\/span><\/strong><\/p>\n

      Official assignments and due dates are at homework page and due dates<\/em><\/td>\n<\/tr>\n

      9\/8<\/td>\n1<\/td>\nReview course contents <\/strong><\/p>\n

      Overview of software engineering<\/strong><\/td>\n

      		Tentatively form teams and projects. Identify communication mechanisms.<\/td>\n<\/tr>\n
      9\/15<\/td>\n2<\/td>\nProcess of Software Engineering <\/strong><\/p>\n

      Describe the problems and challenges of developing software products; Describe steps in the process for developing software products; summarize and compare various models (top-down, incremental, spiral etc.); the Capability Maturity Model<\/td>\n

      		Finalize teams.<\/p>\n

      List informal requirements of project, describe the challenges, explore feasibility; volunteer skill specialization (e.g. Java) Summarize process alternatives; apportion feasibility retirement.<\/p>\n

      Investigate legacy system; develop program to learn tools.<\/p>\n

      Develop SCMP and prototype<\/td>\n<\/tr>\n

      9\/22<\/td>\n3<\/td>\nSoftware Project Management<\/strong><\/p>\n

      Introduce project management concepts, development metrics and risk management; the Personal Software Process. Refine informal requirements. Implement prototype parts. Scheduling, quality assurance, configuration management; inspection techniques I.<\/td>\n

      		Draft project management plan, metrics, describe risks with retirement Apportion detailed risk retirement tasks; draft project management plan; draft configuration management plan. Refine informal requirements. Apportion skill matrix.<\/p>\n

      Reverse engineer legacy system.<\/p>\n

      Develop SPMP<\/td>\n<\/tr>\n

      9\/29<\/td>\n4<\/td>\nRequirements Analysis I<\/strong><\/p>\n

      Introduce the concept of system engineering; describe requirements analysis and C-requirements<\/td>\n

      		Build prototypes and proof-of-concept experiments.<\/p>\n

      Develop SRS<\/td>\n<\/tr>\n

      10\/6<\/td>\n5<\/td>\nRequirements Analysis II<\/strong><\/p>\n

      Describe and apply D-requirements<\/td>\n

      		Define requirements for project<\/p>\n

      Develop SRS<\/td>\n<\/tr>\n

      10\/20<\/td>\n6<\/td>\nDesign I: Essentials <\/strong><\/p>\n

      Design principles and concepts; Define “architecture” and review alternatives<\/td>\n

      		Specify design for project modules; Decompose project into 3-7 modules for group execution. Specify interfaces.<\/p>\n

      Develop SDD<\/td>\n<\/tr>\n

      10\/27<\/td>\n7<\/td>\nDesign II: Design Techniques <\/strong><\/p>\n

      Describe alternative design methods; match with requirements<\/td>\n

      		Develop SDD<\/td>\n<\/tr>\n
      11\/3<\/td>\n8<\/td>\nImplementation<\/strong><\/p>\n

      Programming standards etc.<\/p>\n

      Code inspections<\/td>\n

      		<\/td>\n<\/tr>\n
      11\/10<\/p>\n

      online<\/td>\n

      		9<\/td>\nIntegration<\/strong><\/p>\n

      Describe integration and unit testing<\/td>\n

      		<\/td>\n<\/tr>\n
      11\/10<\/td>\n10<\/td>\nTesting<\/strong><\/p>\n

      Describe testing strategies and techniques; inspection techniques<\/p>\n

      Review for midterm<\/td>\n

      		<\/td>\n<\/tr>\n
      11\/17<\/td>\n11<\/td>\nMidterm<\/em><\/td>\n <\/em><\/td>\n<\/tr>\n
      12\/1<\/td>\n12<\/td>\nMaintenance <\/strong><\/td>\n<\/td>\n<\/tr>\n
      12\/8<\/td>\n13<\/td>\nProject Presentations<\/strong><\/td>\nProject due; Present results<\/td>\n<\/tr>\n
      12\/12<\/td>\n<\/td>\n(no class)<\/strong><\/td>\nIndividual project assessments due<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
      Tools<\/strong> <\/strong><\/p>\n

      Here are some (mostly free) tools to consider<\/p>\n

      For configuration management: Freepository , SourceForge<\/a><\/p>\n

      Forums — past and present<\/strong><\/p>\n

      Spring 1999; Summer 1999; Fall 1999; Spring 2000; Fall 2000; Spring 2001; Spring 2002;<\/p>\n

      Fall 2002; Spring 2003<\/span>; Summer 2003; Fall 2003; Spring 2004<\/p>\n

      Fall 2004: Spring 2005<\/p>\n

      Fall 2005:<\/p>\n

      Post message: 673F05@yahoogroups.com<\/p>\n

      Subscribe: 673F05-subscribe@yahoogroups.com or go to the site at http:\/\/groups.yahoo.com\/group\/673F05\/<\/p>\n","protected":false},"excerpt":{"rendered":"

      Last updated: October 28, 2005. The most recent updates are usually in red type Description: Techniques for the construction of reliable, efficient and cost-effective software.\u00a0 Requirements analysis, software design, programming methodologies, testing procedures, software development tools and management issues.\u00a0 Students design and implement a system in a group project.\u00a0 Laboratory course. Background of the Instructor […]<\/p>\n","protected":false},"author":2828,"featured_media":0,"parent":22,"menu_order":3,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/pages\/43"}],"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=43"}],"version-history":[{"count":1,"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/pages\/43\/revisions"}],"predecessor-version":[{"id":44,"href":"https:\/\/sites.bu.edu\/braude\/wp-json\/wp\/v2\/pages\/43\/revisions\/44"}],"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=43"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}