Upon course completion, a successful student should be able to:

• Describe basic concepts of software engineering practice
  
  
• Describe the various phases of the software lifecycle, the activities that take place in each phase, and what is created in each
  
  
• Explain the purpose of requirements gathering and specification
  
  
• Effectively utilize UML class and sequence diagrams to describe object-oriented software designs
  • distinguish between high-level (sequence) and low-level (class, sequence) designs
  • describe the elements of UML class and sequence diagrams create UML class diagrams (in Enterprise Architect or hand-drawn)
  • explain/distinguish/demonstrate the use of generalization and realization relationships in UML class diagrams
  • explain/distinguish/demonstrate the use of composition and shared aggregation relationships [not covered]
  • explain/distinguish/demonstrate the use of usage/dependency relationships
  • demonstrate iteration in a sequence diagram [not covered]
  • demonstrate selection in a sequence diagram [not covered]
  • demonstrate the appropriate use of end roles, multiplicity, and names in a class diagram
  • describe how multiplicity greater than 1 on an end role affects the code generated by Enterprise Architect (i.e. it causes EA to generate a collection class to hold references to the end role datatype; the type of collection class depends on how you configure EA's default collection class)
    
    
• Use Enterprise Architect to

  • create UML class diagrams

  • create UML sequence diagrams

  • transform UML class diagrams to source code

  • transform source code to UML class diagrams

• Synchronize detailed object-oriented design models with changed source code generate Java code from an Enterprise Architect class model

• Generate an Enterprise Architect class model from an existing Java project

• Synchronize Java code from a modified Enterprise Architect class model

• Synchronize an Enterprise Architect class model from a modified Java project
  
  

• Use a revision control system to maintain versions of source code and related design documents
  • explain why revision control systems are critical to software development
  • describe the lock-modify-unlock approach for managing conflicts
  • describe the copy-modify-merge approach for managing conflicts
  • describe Git's distributed approach for managing conflicts
  • demonstrate how conflicts are resolved with Git list advantages/disadvantages between the lock-modify-unlock and copy-modify-merge approaches for managing conflicts
  • use a Git server and the Git client to manage version control for a multi-developer project
  • explain the concept and purpose of tagging a repository
  • explain the concept of pushing a file to a remote repository
  • explain the concept of pulling a file from a remote repository
    
    
• Create an installable software package using an automated build tool (ANT)
  • explain the purpose for automated build tools such as ANT use Eclipse to create an executable .jar file
  • explain the purpose of the manifest file used in a .jar file use Eclipse to create an build script (build.xml)
  • use Eclipse to create an ANT build script (buildjar.xml) for creating .jar files
    
    
• Validate the behavior of java classes with simple unit tests create unit test classes that can be executed within the JUnit framework
  • write simple JUnit test methods that validate the operation of an application
  • use JUnit to run test class methods
  • run JUnit outside of Eclipse via ANT [not covered]
  • use a build script to create html-based JUnit test reports [not covered]
  • explain the purpose of the annotation @Test
  • use methods from the org.junit package such as assertEquals() and fail() in unit test methods to indicate test failure
    
    
• Interpret requirements documented as Use Cases
  • perform use case textual analysis for a given use case
  • effectively transform use cases into a high level design (high-level sequence diagram)
  • distinguish between functional and non-functional requirements [not covered]
  • describe and demonstrate the use of a scenario
  • describe and demonstrate the use of an actor
  • describe and demonstrate the use of a goal
  • describe and demonstrate the use of an alternate flow
  • explain how pre-conditions and post-conditions are used in use cases
  • transform requirements and use cases into high-level object-oriented
  • design models represented by high-level sequence diagrams
    
    
• Create UML high-level sequence diagrams in Enterprise Architect
  • define a boundary object and draw its symbol
  • define an entity object and draw its symbol
  • define a control object and draw its symbol
  • define a actor and draw its symbol
  • distinguish between actors, boundary, entity and control objects
  • identify which objects may interact with an actor
  • identify which objects may interact with each other
    
    
• Cohesion and Coupling
  • define cohesion
  • define coupling
  • explain why cohesion and coupling are important design considerations
    
    
• Transform high-level object-oriented designs to detailed design models, including low-level class and sequence diagrams
  
  
• State diagrams
  • explain what an event in a state diagram represents
  • explain what an action in a state diagram represents
  • explain what a state in a state diagram represents
  • explain what a guard in a state diagram represents
  • demonstrate proper use of events, actions, states and guards in a state diagram
  • interpret state diagrams
  • implement a state machine in java from a state diagram