Non-Exam Based Assessment
Cover Sheet
Course Name | System Architecture & Integration | Course Code | CIS 3303 |
Assessment | Integration Project | Handing out Week | 28th-Nov |
To be submitted in: | Week 15 | ||
Maximum Marks | 100 Marks | Percentage of Final Grade. | 25% |
This assessment will assess the following Course learning outcomes:
CLO1 | CLO2 | CLO3 | CLO4 | CLO5 | ||
Question No. | √ | √ | √ | √ | ||
· The entire project/case study/poster is designed and developed by me (and my team members). · The proper citation has been used when I (and my team members) used other sources. · No part of this project has been designed, developed or written for me (and my team members) by a third party. · I have a copy of this project in case the submitted copy is lost or damaged. · None of the music/graphics/animation/video/images used in this project have violated the Copy Right/Patent/Intellectual Property rights of an individual, company or an Institution.
Student Signature: Date:
| ||||||
For Examiner’s Use Only
Question No. | Task A | Task B | Task C | Task D | Total Marks |
Marks Allocated | 25 | 25 | 25 | 25 | 100 |
Marks Obtained (Student 1) | |||||
Marks Obtained (Student 2) | |||||
Marks Obtained (Student 3) |
Process Specification
HCT maintains 14 different libraries within each college. HCT wishes to integrate all college libraries within one centralized system using a state of the art SOA architecture. In particular, the system will record the books owned by the library and will record who has borrowed what books. Before someone can borrow a book, he or she must show a valid ID card, which is checked to insure that it is still valid against the student database maintained by the registrar’s office (for student borrowers), the faculty/staff database maintained by the personnel office (for faculty/staff borrowers). The system must also check to ensure that the borrower does not have any overdue books or unpaid fines before he or she can borrow another book. Every Monday, the library sends emails to those people with overdue books. If a book is overdue by more than two weeks, a fine will be imposed and the system will automatically notify the user about the fine by sending an email. Sometimes, books are lost or returned in damaged condition. The manager must then remove them from the database and ask the person responsible for the damage to pay the value of the damaged property.
Task A [25 Marks]: Create a Business Process Modeling Notation Diagram that will model the above process. For this task, you can make any logical assumptions that you may decide is necessary for completing the model. If any assumptions are made you must document them by providing some explanations/justifications. Use any professional modelling tool (e.g. Microsoft Visio) to design the process model.
Task B [25 Marks]: Identify and match a web service for each activity (or activities) presented in your BPMN diagram. Provide adequate documentation to describe the name of the service and its functionality.
Task C [25 Marks]: Create a service-oriented architecture that will support the implementation and integration of the above web service descriptions. For each service used in the SOA diagram clearly identify the type and role of the service within the SOA architecture i.e. Enterprise Business processes, Business Services, Domain Services, Utility Services, Integration services, External Services, Foundation Services.
Task D [25 Marks]: Validate your model by showing the interaction of these services. Specifically use examples of XML documents to show the movement of data between these services.
TASK A | BPMN [25 Marks] | ||||
Grades allocated | 0-10 | 10-15 | 15-20 | 20 -25 | |
Not Attempted or the attempt is the result of insignificant effort. | Poor Some effort. A solution has been provided but many areas need extra attention. | Good Sufficient effort (most elements covered). The model, for the most part represent a significant effort but some areas need further attention or and improvement. | Excellent The model uses correct notation. It is implemented and presented using an appropriate modeling tool. The model accurately reflects the scenario presented. | ||
Grades Earned | |||||
Total (out of 25): |
TASK B | Web Service Identification and Documentation [25 Marks] | ||||
Grades allocated | 0-10 | 10-15 | 15-20 | 20 -25 | |
Not Attempted or the attempt is the result of insignificant effort. | Poor Some effort. A mapping schema is attempted but many areas need extra attention. | Good Sufficient effort. Most web services are correctly mapped to an activity. Web service labels and their functionality are for the most part correct. The result of a significant effort. | Excellent Each activity is mapped to a web service. Each service is clearly labeled and proper description of its functionality has been provided. | ||
Grades Earned | |||||
Total (out of 25): |
TASK C | SOA [25 Marks] | ||||
Grades allocated | 0-10 | 10-15 | 15-20 | 20 -25 | |
Not Attempted or the attempt is the result of insignificant effort. | Poor Some effort. An SOA has been provided but many areas need extra attention. The model presented or the most part is unrealistic. | Good Sufficient effort (most elements covered). The SOA presented for the most part accurately implements the needs of the system – the result of a significant effort but some areas need further attention or and improvement. | Excellent An SOA architecture is presented that accurately reflects the system needs. Each service has been correctly identified with a proper type. | ||
Grades Earned | |||||
Total (out of 25): |
TASK D | XML [25 Marks] | ||||
Grades allocated | 0-10 | 10-15 | 15-20 | 20 -25 | |
Not Attempted or the attempt is the result of insignificant effort. | Poor Some effort. There inconsistencies with the data interactions between the web services. The resulting outcome of the interactions may be unclear. | Good Sufficient effort (most elements covered). Most of the data interactions between the web services are correctly presented with xml documents. The result of a significant effort. | Excellent The data interactions between the web services has been clearly documented using xml documents. The sequence of interactions and the relevancy of data are logical and correctly cover the needs of the system. | ||
Grades Earned | |||||
Total (out of 25): |