Scribd
Upload
5 views

D2 Report Sample

Uploaded by

junaid.developer10
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
5 views

D2 Report Sample

Uploaded by

junaid.developer10
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 15

 

Software  Analysis  and  Design  Case  Study  


A  System  for  Monitoring  Students’  Performance  in  Schools  (D2)  
 

(Part  1)  
 
UML  Use  Cases  diagram  for  the  ‘StudentMonitoringSystem’  
 

A  UML  (Unified  Modelling  Language)  Use  Case  diagram  has  been  produced  for  this  Student  
Monitoring  System  to  demonstrate  the  system's  behaviour,  convey  the  system's  
requirements,  and  illustrate  multiple  ways  in  which  users  may  interact  with  the  system.  
Teachers,  Parents,  and  the  Administrator  are  the  actors  interacting  with  the  system  in  this  
diagram.  
 

 
Figure 1: A  UML-­‐use  case  diagram  (UCD)  containing  5-­‐7  use  cases  from  the  D1  
StudentMonitoringSystem  requirements  table.  

  1  
 
 

 
 
Use  Cases  (Tables)  
 
 
Use  Case  Tables  have  been  used  to  expand  on  the  diagram's  context,  to  document  one  or  
more  use  cases,  and  to  capture  the  goals  of  stakeholders.  These  step-­by-­step  templates  
serve  as  a  starting  point  for  additional  exploration  into  how  each  system  function  will  
accomplish  its  stated  aim  in  these  individual  use  cases.  
 
1.   Use  Case  Table:  Register  and  Create  Account  
 
 

  2  
 
 

 
 
2.   Use  Case  Table:  Create  and  Manage  Classes    
 
 

  3  
 
 

 
 
Main  Sequence  Diagrams  for  the  ‘StudentMonitoringSystem’  
 
 
Sequence  Diagrams  are  generally  used  to  detail  the  interaction  and  order  between  the  
sequential  operations  of  how  a  set  of  objects  function  together  and  their  ultimate  outcome.  
They  are  also  used  to  visually  illustrate  the  use  cases.  
 
Diagram  1.   R4:  Register  and  Create  Account  (as  a  User)  
 

  4  
 
 

 
 
 
Diagram  2.   R5:  Create  and  Manage  Class  (as  a  Teacher)  
 

  5  
 
 

 
 
Diagram  3.   R8:  Request  and  Schedule  Virtual  Meetings  (as  a  Teacher)  
 

  6  
 
 

 
 
Diagram  4.   R9:  Register  and  Manage  Account  (as  a  Parent)  
 

  7  
 
 

 
 
Diagram  5.   R11:  Add  Query/Note  (as  a  Parent)  
 
 

  8  
 
 

 
 
(Part  2)  
Enriching  a  given  analysis  and  design  for  the  ‘StudentMonitoringSystem’  
 
Key:   -­  Shaded  Tables  have  been  revised  and  enriched  from  D1  requirements  table.  

 
(Functional)  Requirement  Table:  

(Non-­Functional)  Requirement  Table:  


 

  9  
 
 

 
 
 
UML  class  diagram  for  the  ‘StudentMonitoringSystem’  
 
Class  diagrams  are  useful  for  designing  a  software  system's  structure.  Class  diagrams  are  
blueprints  that  depict  a  detailed  static  representation  of  the  objects  that  make  up  the  system.  
Class  diagrams  also  show  the  relationships  between  the  objects,  as  well  as  what  they  do  
and  what  services  they  provide.  
 
 
 

  10  
 
 

 
 
Interfaces  (Prototyping)  for  the  ‘StudentMonitoringSystem’  
 

Prototyping  is  used  to  visualise  the  system  by  designing  and  building  user  interfaces  in  order  
to  explore  the  system's  solution  space.  Interfaces  are  important  in  defining  the  system's  
boundaries  and  determining  the  system's  dependencies.  
Welcome/Registration  System  Homepage  

 
Parent  Registration/Sign  Up  

  11  
 
 

 
 
Teacher  Registration/Sign  Up  

 
 
Login  Portal  for  Parents  

  12  
 
 

 
 
Login  Portal  for  Teachers  

 
Login  Portal  for  Admin  

  13  
 
 

 
 
Parent  Homepage/Dashboard  

 
 
Teacher  Homepage/Dashboard  

  14  
 
 

 
 
Admin  Homepage/Dashboard  

  15  

You might also like