《Software Modeling and Analysis》课程教学大纲

1、“Software Modeling and Analysis”Course Teaching Syllabus、Basic Course InformationCourse Name（Chinese） 软件建模与分析Course Name（English）Software Modeling and AnalysisCourse Type1:Major CoursesCourse Nature2Compulsory CourseLanguage of Instruction3:All in EnglishTeaching Semester4Credit3Teaching Periods and

2、 AllocationTotal PeriodsTeachingPracticeExtracurricular48321616Applicable MajorsSoftware EngineeringTextbooksCollegesSchool of Computer & SoftwareHYPERLINK ./././././AppData/Local/youdao/dict/Application//resultui/html/index.html l /javascript:;PrerequisiteHYPERLINK ./././././AppData/Local/yo

3、udao/dict/Application//resultui/html/index.html l /javascript:;CourseSoftware Engineering, Object-Oriented ProgrammingFollow-up CourseSoftware Architecture and DesignHYPERLINK ./././././AppData/Local/youdao/dict/Application//resultui/html/index.html l /javascript:;CourseHYPERLINK ././.

4、/././AppData/Local/youdao/dict/Application//resultui/html/index.html l /javascript:;IntroductionBasic Orientation of Course: Improve students ability of cooperation, data access, document writing, analysis, and practical problem-solving ability.Core Learning Outcomes: Make students master the

5、 ability of using object-oriented thinking and UML to acquire, model and analyze system requirements, and write excellent requirements documents.Main Teaching Methods: Class explanation, group discussion, experiment design, after class practice.Syllabus Update Time2020.08PS: 1. Course Type: Select a

6、nd fill in General Education Core Courses/General Education Development Courses/General Courses/Discipline Basic Courses/Major Courses/Professional Elective Courses/Professional Practice/Quality Development.Course Nature: Select and Fill in Selective Course/Compulsory Course.Language of Instruction:

7、 Select and Fill in Chinese/Bilingual/ All in English or Other Languages.、Course ObjectivesNumberCourse Objectives(Refer to Training Objectives, Graduation Requirements and Course Orientation)Index Points of Graduation Requirement to be Supported 1Ways to Achieve1.1Master the basic theoretical knowl

8、edge of software requirements analysis, master the basic process, importance and characteristics of system analysis;1.4 Systematically master the basic theory and professional knowledge of software engineering, including computer hardware, software and system, etc., have the ability to understand co

9、mplex engineering problems in software engineering, and be able to use the knowledge learned to solve software engineering problems.Learning theoretical knowledge1.2Master the relationship and difference between each model, and be able to use the knowledge of these three aspects to solve the problem

10、s encountered in system analysis;1.4 Systematically master the basic theory and professional knowledge of software engineering, including computer hardware, software and system, etc., have the ability to understand complex engineering problems in software engineering, and be able to use the knowledg

11、e learned to solve software engineering problems.Learning theoretical knowledge2.1Be able to use the basic theory and design method of software requirements analysis, research and design feasible solutions for complex engineering problems in front-end software development, and analyze and demonstrat

12、e the solutions.2.2 Apply professional knowledge in the field of software engineering, and be able to find, raise and analyze problems by using engineering methods such as charts and charts according to the actual engineering cases given;Learning theoretical knowledge and case analysis2.2Have the ab

13、ility of modeling and analyzing information system; master the ability of writing requirement documents.2.2 Apply professional knowledge in the field of software engineering, and be able to find, raise and analyze problems by using engineering methods such as charts and charts according to the actua

14、l engineering cases given;Learning theoretical knowledge and case analysis3.1Be able to solve complex business problems, give full play to the ability of organization and coordination, effectively communicate with team members and solve problems in practice.11.1 Master the principles of technical ma

15、nagement, personnel management and engineering management, and master the methods of economic management and decision-making;Learning theoretical knowledge and case analysis3.2Master the project development cycle and various development methods. Familiar with the role of each role in project develop

16、ment, with preliminary team management ability11.3 Be able to apply engineering management principles and economic decision-making methods in a multidisciplinary environment, and have preliminary experience and ability in software engineering project management.Experiment design and case analysisPS:

17、1. to be Supported: Optional. They are required for Professional Certification and courses with Index Points of Graduation Requirement. Otherwise, they can be left blank.、Theoretical Teaching ContentChapter TitleTeaching ContentTeaching PeriodsIdeological and Political Integration Points1Expected Ou

18、tcome of Students Learning2Teaching Methods3Course ObjectivesChapter oneSoftware System1. Introduce the basic concepts of system, software, software system and platform, and their differences and relations.2. Describe the classification of information system and the characteristics of each category3

19、. Introduce the origin and importance of software engineering and the necessity of using object-oriented system analysis.2 hours1. Understand the difference between system and software. Understand the differences between systems and platforms.2. Master the differences between different information s

20、ystems.3. Know the important attributes of software.4. Understand the origin and importance of software engineering.lecturesCourse objective 1.1Chapter twoSoftware life cycle1. Introduce each stage of softwares whole life cycle and the tasks to be completed in each stage.2. Introduce the development

21、 mode related to life cycle in detail.3. Introduce the concept of RUP and UML.4. Briefly introduce the composition of the project development team.4 hours1. Understand the basic system development life cycle and its four stages.2. Be familiar with the evolution of system development methods.3. Under

22、stand RUP and its extensions.4. Understand why UML is needed to model our system.5. Be familiar with different roles of project team.lecturesCourse objective 1.2Chapter threeObject oriented technology1. Introduce the concept of object2. Introduce three object-oriented mechanisms: encapsulation, inhe

23、ritance and polymorphism.2 hours1. Understand the basic principles of object-oriented;2. Master the definition of class and object;3. Understand instance variables, attributes and associations;4. Understand the method, operation and polymorphism;5. Learn how to organize classes into inheritance hier

24、archies;Lectures, demonstrationCourse objective 2.1Chapter fourIntroduction to UML1. Introduce the concept, necessity, origin and history of UML2.Introduction of UML syntax diagram.3. Introduce the syntax and precautions of activity diagram, use case diagram, class diagram, sequence diagram and stat

25、e diagram in detail.6 hours1. Understand the role and history of UML;2. Understand the basic syntax of UML and the syntax of various common diagrams.3. Master the syntax of activity diagram, use case diagram, class diagram, sequence diagram and state diagram.Lectures, demonstration and discussionCou

26、rse objective 2.2Chapter fiveProject Initiation1. 1. Introduce how to start a project, focus on the concept of project sponsor and project request.2. Discuss the feasibility of system development from different dimensions.3. Choose the project development method according to the characteristics of t

27、he project.4. Introduce how to estimate the project size, development cycle and development cost.5. How to create and manage workflow, how to decompose project, how to make project development plan.6. Discuss how to determine the development team according to the characteristics of the project, how

28、to select the members and how to avoid the risks in the development4 hours1. Understand the importance of information systems.2. Be able to create system requests. Learn how to assess technical, economic and organizational feasibility.3. Be able to carry out feasibility analysis. Learn how some orga

29、nizations choose projects. Familiar with estimation. Ability to develop project work plan.4. Understand why project teams use time constraints. Be familiar with how to staff the project.5. Understand how computer aided software engineering, standards and documentation can improve project efficiency.

30、Lectures, demonstration and discussionCourse objective 2.2Chapter sixDetermination of requirements1. Introduce the definition, level and classification of requirements;2. Focus on the methods of how to find requirements and the advantages and disadvantages of each method;3. Introduce how to write th

31、e system proposal document;4 hours1. Learn how to create a requirement definition.2. Familiar with requirement analysis technology.3. Know when to use each requirement analysis technique.4. Understand how to collect needs through interviews, JAD meetings, questionnaires, document analysis and observ

32、ation.5. Know when to use various requirements gathering techniques.Lectures, demonstration and discussionCourse objective 3.2Chapter 7Functional modeling1. Introduce UML activity diagram, and use activity diagram to model business.2. Focus on the concept of use cases, points for attention and mista

33、kes.3. Introduce the syntax of use case diagram.4. Focus on the description of use cases.2 hours1. Understand the rules and style guide of activity diagram.2. Understand the rules and style guidelines for use cases and use case diagrams.3. Understand the process used to create use cases and use case

34、 diagrams4. Be able to use activity diagram, use case and use case diagram to create function model.Lectures, demonstration and discussionCourse objective 3.2Chapter 8Structural modeling1. Introduce the methods and related concepts of object-oriented analysis.2. Introduce common object recognition m

35、ethods: text analysis, CRC card, common object list and pattern.3. Introduce the syntax of class diagram and object diagram.4. Introduce the steps of structural modeling.2 hours1. 1. Understand the rules and style guidelines for creating CRC cards, class diagrams and object diagrams.2. Understand th

36、e process of creating CRC card, class diagram and object diagram.3. Be able to create CRC card, class diagram and object diagram.4. Understand the relationship between structure model and use case model.Lectures, demonstration and discussionCourse objective 1.2Chapter 9Behavior modeling1. Introduce

37、the related concepts of behavior model; the necessity of behavior modeling and the relationship between structural model and functional model.2. Introduce the syntax of sequence diagram and state diagram.3. Focus on the steps of behavior modeling, the improvement and supplement of structural model.4

38、. Briefly introduce the management of analysis work.2 hours1. Understand the sequence diagram and communication diagram as well as the rule and style guide of behavior state machine.2. Understand the process used to create sequence and communication diagrams and behavior state machines.3. Be able to

39、 create sequence and communication diagram and behavior state machine.4. Understand the relationship between behavior model and structure and function model.Lectures, demonstration and discussionCourse objective 3.1Chapter 10Requirement description1. Introduce the necessity and guiding principle of

40、writing requirement specification document.2. Introduce the template of requirement specification document and how each part of the template should be expressed.4 hours1. Understand why we need to describe requirements.2. Understand the characteristics of requirement specification.3. Master some gui

41、ding principles of writing requirements.4. Learn how to use SRS template.Lectures,Course objective 3.2PS: 1. Ideological and Political Integration Points: Write at least 3 points that the ideological and political education content and professional education content will be organically integrated in

42、 this course teaching (the same below).Expected Outcome of Students Learning: describe the level of knowledge, ability, or accomplishment that a student should acquire after completing this section (the same below).Teaching Methods: including lectures, discussions, cases, demonstrations, etc., but n

43、ot limited to listed methods. Listed points should be based on the actual needs of the course.、Practical (Experiment or Practice) Teaching1NumberName of Experiment or Practice ProjectTeaching ContentTeaching Periods Experiment or Practice Type2Ideological and Political Integration PointsExpected Out

44、come of Students LearningCourse Objectives1Project PlanningUse modeling tools for project size estimation, cost calculation and project planning using GATT diagram.2Verifiability1. Master the method of project estimation;2. Be familiar with the technology of how to make project planCourse objective

45、1.22Business activity modeling1. Select a system for project research. According to the collected project materials, use modeling tools to model business activities.2. Need to draw business use case diagram, business activity diagram, business sequence diagram and conceptual model.2Verifiability1. F

46、amiliar with the concept of business activity modeling.2. Master the drawing method of use case diagram, activity diagram and sequence diagram.3. Master the use of modeling tools.Course objective 2.13Business domain modeling1.Create business domain modeling using EA tools.2. The concept model needs

47、to be expressed by class diagram.2Verifiability1. Be familiar with the concept of business domain modeling.2. Master the drawing method of class diagram.Course objective 2.14functional modelUse EA to model the function of the system and draw the system use case diagram.For each use case, use case de

48、scription.2Verifiability1. Master the syntax of use case diagram, and be familiar with the concepts of role, boundary and use case.2. Master the relationship between use cases.3. Master the basic specification of use case description.Course objective 2.25Structural modelUse EA to model the structure

49、 of the system and draw the system class diagram.You need to give the properties and methods of classes, and the relationship between classes2Verifiability1. Master the grammar of class diagram;2. Master the relationship and expression between classes;Course objective 3.16Behavior model sequence dia

50、gram1. Use modeling tools to model behavior and draw system sequence diagram.2. According to the sequence diagram, supplement or modify the previous model to make them consistent.2Verifiability1. Master the grammar of sequence diagram;2. Understand the relationship between sequence diagram, class di

51、agram and use case diagram;Course objective 3.17Behavior model state diagram1. Use modeling tools to conduct behavior modeling and draw system state diagram.2. According to the state diagram, supplement or modify the previous model to make them consistent.2Verifiability1. Master the grammar of state

52、 diagram;2. Understand the relationship between state diagram, class diagram and use case diagram;Course objective 2.18Writing requirementsAccording to the SRS template, all the previous contents and achievements are sorted into system requirements documents2ComprehensivenessMaster the specific writ

53、ing methods and precautions of requirement documents.Understand the differences between functional requirements and non functional requirements in expression.Course objective 3.2PS: 1. This form can be used for in-class practical teaching or for a comprehensive practical course. 2. Experiment Type:

54、select and fill in Verifiability/Comprehensiveness/designability; Practice Type: select and fill in Understanding Practice/Production Practice/Graduation Practice.、HYPERLINK ./././././AppData/Local/youdao/dict/Application//resultui/html/index.html l /javascript:;CourseHYPERLINK ./././././AppD

55、ata/Local/youdao/dict/Application//resultui/html/index.html l /javascript:;Evaluation（1）The Corresponding Relationship among Assessment Contents, Assessment Methods and Course ObjectivesCourse ObjectivesAssessment ContentsThe Course Objectives Account for the Proportion in Each Assessment Met

56、hod1HYPERLINK ./././././AppData/Local/youdao/dict/Application//resultui/html/index.html l /javascript:;DailyHYPERLINK ./././././AppData/Local/youdao/dict/Application//resultui/html/index.html l /javascript:;PerformanceCourse TasksMid-term ExaminationFinal Examination1.1Master the basic

57、 theoretical knowledge of software requirements analysis, master the basic process, importance and characteristics of system analysis;10%20%20%30%1.2Master the relationship and difference between each model, and be able to use the knowledge of these three aspects to solve the problems encountered in

58、 system analysis;10%20%20%20%2.1Be able to use the basic theory and design method of software requirements analysis, research and design feasible solutions for complex engineering problems in front-end software development, and analyze and demonstrate the solutions.15%15%20%15%2.2Have the ability of

59、 modeling and analyzing information system; master the ability of writing requirement documents.15%15%20%15%3.1Be able to solve complex business problems, give full play to the ability of organization and coordination, effectively communicate with team members and solve problems in practice.20%20%10

60、%10%3.2Master the project development cycle and various development methods. Familiar with the role of each role in project development, with preliminary team management ability30%10%10%10% Total100%100%100%100%Weight of Each Assessment Method in the Total Score (Self-assigned)10%10%20%60%PS: 1.The