Project Related Issues

1
Project Related Issues
2
Requirements Design
3
Consistency

• Between textual descriptions and figures
• Section 3.1 mentions stakeholder tester and
  relevant government agencies, which are not shown
  in Figure 2
• Among different diagrams
• There is a use case missing for the
  dependency/association ending at Update/Cancel
  Meeting and Conflict Resolution
• In specification sequence diagram, the object
  Network has no corresponding class in the
  class diagram
• Among different phases
• How is the potential issue related to Handle
  Negotiations in the preliminary understanding
  being resolved in the improved understanding?
• Between use case template and use case diagrams
• The use case templates are simpler than
  corresponding use case diagram (detailed view)
• Between use case diagram and sequence diagram
• Use case diagram Security System Detailed
  View and sequence diagram User - Security
  System Interaction are inconsistent, i.e.,
  E-Lock and Sensor are actors and objects
  respectively

4
Difference

• Functional and non-functional requirements
• For NFRs in section 6.2, SNFR - 01, SNFR - 03,
  SNFR - 07 and SNFR - 08 seem FRs to me
• System functional dependency diagram
• I am not sure in the System Functional
  Dependency diagram whether agents of the system
  should appear
• Domain, requirements and specifications
• It is good that you can differentiate among
  domain, requirements and specifications, which
  has the flavor of requirements engineering
  course
• Use case diagram has been used in the Domain,
  Specification and Implementation, what is their
  difference. More specifically, an extra actor
  Admin in specification use case diagram and an
  extra actor Controller in implementation use
  case diagram
• Enterprise requirements and functional
  requirements
• Would you please let me know the relationship
  between enterprise requirements and functional
  requirements in the report
• Requirements and use cases
• What is the relationship between the Specific
  Requirements and Use Case Diagrams?

5
Correctness

• Use case diagram
• In section 7.2's use case diagram, the relation
  between Plan A Meeting and Confirm/Notify
  seems not ltltinheritsgtgt, and the multiplicity
  seems redundant
• In the use case diagram 5.1, the way that the
  actor Initiator specializes Regular
  Participant, Active Participant and Important
  Participant can not express your intention
• In the use case diagram, only actor HACS has
  directed association with the use case Operate
  HACS Compliant Devices. Why is that?
• Activity diagram
• In the activity diagram 7.2, there should be
  conditions along the arcs going out from the
  decision symbol, i.e. the rhombus
• Sequence diagram
• In the sequence diagram in section 7,3, the
  User, Meeting Initiator and Participant
  need to be stickman symbol
• In the sequence diagram, the symbol for
  Initiator and Participant should be stickman
  symbol
• The label in the UML diagrams not following the
  UML convention, e.g., in Fig.1. bdd package
  appears for UML frame
• Frames are used in the sequence diagram 4.3.1,
  4.3.2 and 4.3.4, but I am not sure of its correct
  usage

6
Correctness (Cont.)

• Class diagram
• In the class diagram in 4.4.2, the multiplicity
  between classes is incorrect. Also what is the
  relation between User and Meeting Member?
• In the Business Class diagram (Figure. 6), the
  way that Initiator specializes, and Meeting Date
  and Meeting Location specializes seems incorrect
• State transition
• For state transition diagram HACS, a loop back
  either to Idle state or Display Menu state is
  necessary, since this is not one-time operation
• SIG
• Figure 2 and 3 use SIG for process
  specification, but activities appear, which is
  not the way to use SIG
• SADT
• In the SADT 4.4.3 and 4.4.4, some of the
  activities do not have input, but only with
  control and mechanism, which seems not reasonable

7
Implementation Demo
8
Issues

• Consistency among requirements, design and
  implementation
• Technologies
• Web application better than stand-alone
  application
• Pairwise comparison of the functionalities and
  non-functionalities among different groups

9
Questions You May Have