Software Engineering Course Mind Map

Structure as follows

• Software Engineering
  • What is software engineering
    • Methods
      • Systematic
      • Disciplined
      • Quantifiable
    • Process
      • Software development
      • Operation
      • Maintenance
  • Main constituent elements
    • People
    • Project
    • Process
    • Methods
    • Tools
    • Software artifacts
  • Driving forces behind software engineering progress
    • Hardware capability
    • Software technology
    • Social needs
    • Level of science and technology
  • The 8 quality factors of software
    • Correctness
      • The degree to which software satisfies the requirements specification
      • The degree to which it achieves user goals
    • Usability
      • Cost of learning and using
        • Operating the software
        • Inputting data
        • Interpreting software output
    • Reliability
      • Probability of completing expected functions
      • Probability of successful operation
    • Efficiency
      • Ability to complete system functions using computer space resources
      • Using computer time resources
    • Maintainability
      • After delivery, through modification, in order to
        • Correct latent defects
        • Improve performance
        • Other attributes
    • Portability
      • Difficulty of installing on different computers
      • Installing in different environments
    • Security
      • Mechanisms to control/protect programs and data from damage, preventing
        • Access
        • Use
        • Modification
        • Destruction
        • Disclosure
    • Reusability
      • The degree to which software components can be applied in multiple contexts
        • Relatively independent in concept
        • Or one or a group of related modules that are relatively independent in function
  • Generic software development process
    • Activities
      • Communication
      • Planning
      • Modeling
      • Construction
      • Deployment
    • Advantages
      • Enhances software development capability
      • Highlights the characteristics of software engineering
      • Has greater flexibility
      • Has greater adaptability
  • UML diagrams used in each phase
    • Project initiation
    • Inception
      • Use case diagram: use cases describing software requirements
      • Activity diagram: representing business processes
      • Interaction diagram: representing the internal implementation of use cases
    • Elaboration
      • Package diagram: representing software architecture
      • Component diagram: representing software architecture
      • Deployment diagram: representing software architecture
    • Construction
      • Class diagram: software detailed design model
      • Interaction diagram: software detailed design model
      • Activity diagram: software detailed design model
      • State diagram: software detailed design model
      • Component diagram: software detailed design model
  • Workflow of the requirements engineering process
    • Requirements engineering planning
    • Requirements elicitation
    • Requirements analysis
    • Requirements specification
    • Requirements validation
    • Summary
  • Use-case-driven requirements elicitation process
    • Define the software problem
    • Create framework use cases
    • Refine use cases
    • Review the use case model
  • Tasks of requirements analysis
    • Based on the requirements elicitation phase
    • Obtain an understanding of software requirements
      • More in-depth
      • More complete
    • Represent software requirements as an analysis model
      • Oriented toward software designers
      • Easy to modify
      • Maintain
  • Use-case-driven requirements analysis process
    • Requirements priority analysis
    • Use case analysis
    • Analysis model review
    • Rapid prototypes built to assist requirements analysis
  • Principles that software design should follow
    • Abstraction and stepwise refinement
    • High cohesion and loose coupling
    • Information hiding and separation of concerns
  • Workflow of the software design process represented with UML activity diagrams
    • Design planning
    • Architecture design
    • Human-computer interaction design
    • Detailed design
    • Design integration and verification
    • Summary
  • Main activities of the user interface design process
    • User analysis
    • Task analysis and modeling
    • Conceptual design
    • Interface flow design
    • Interface refinement
  • Main activities of the detailed design process
    • Use case design
    • Subsystem design
    • Component design
    • Class design
    • Data model design
    • Design integration and verification
  • Testing and principles of software testing
    • Tasks
      • Check whether the software satisfies the requirements specification
      • Discover as many latent defects as possible in the software before the software artifact is delivered
      • Reduce the cost of corrective maintenance after delivery
    • Principles
      • Testing is an ongoing process, not a phase
      • Testing must be planned, controlled, and provided with sufficient time and resources
      • Testing should be prioritized
      • Testing should have a focus
      • Testing is not to prove the correctness of a program, but to prove that it does not work
      • Testing cannot be exhaustive; testing can stop when test adequacy is satisfied
      • Testing is a friend of development, not an enemy of development
      • Testers should test impartially and record and report defects truthfully
      • Test automation can solve some problems, but not all
      • Testing should not only include functional verification, but also verification of the following aspects
        • Performance
        • Reliability
        • Maintainability
        • Security
  • Test cases
    • Concept
      • Input data of the test design
    • Contents
      • Generated input data
      • Program execution conditions
      • Test steps
      • Expected output
  • α and β testing
    • α testing: testing conducted by system developers, without user participation
    • β testing: testing by users, usually without developers present
  • Classification of software maintenance
    • Corrective maintenance
    • Perfective maintenance
    • Adaptive maintenance
    • Preventive maintenance
  • What levels of work does software restructuring include
    • Document restructuring
    • Restructuring
    • Reverse engineering
    • Reengineering
  • Factors in user interface design
    • Practicality
    • Flexibility
    • Interface complexity and reliability

I tidied up the mind map, as follows