By complying with the objectives and course learning outcomes of the course we designed the practical assessment components which will help you to achieve specialization in analyzing and design a system including all its inside mechanism. In line with 1st practical component, the 2nd practical component is to design the system using your expertise on designing tools and it is based on finalized requirements. Each question carries equal one (1) mark and presentation is five (5) marks which will sum-up of 15 marks in total. However, question-1 is just to update it will not carry any mark.

1. Update Part 1 of the assignment including activities to even/response table

Apart from what you see appropriate, you should note the feedback that you have received during your presentation as well as in your written report on part 1 of the case study and adjust as necessary.

2. Develop Process Specifications for the core components of your system

These specifications should be for lowest level of processes that appear on your DFDs. You should specify two separate processes for each of three pSpec types - structured English, decision table and decision tree. Thus, you will provide six pSpecs for six different lowest level processes for the assignment.

3. Develop an Entity Relationship Diagram (ERD) and show normalization (up to 3rd Normal Form)

Examine the lectures for some ideas about normalization. If you cannot see how you might normalize your ERD, have a look in your textbook. You can also refer to other texts in the library on the topic. The Internet is a useful source of information. Be selective when you do research on the Internet and look for credible sources. Ask questions, such as do the articles match lecture materials? If not, why? Your research shouldnt normally contradict lecture materials.

4. Develop two/three Use Case Diagrams for core features of your system

Think about core stakeholders in identifying core features of your system. Core stakeholders might well be presenting core events that represent the essence of your system. Think about other models that you have developed which reflect the essential or core purpose/s of the system. Your Use Cases and Use Case Diagrams should match those models.

5. Specify Use Case Descriptions for some (minimum of two) important Use Cases

Think about where you might discover the narratives that could describe your Use-cases. The assessor will be checking to see if they match.

6. Develop the Class Diagram for your system

Dont forget to think about the models with which the Class Diagram should match.

7. Develop an Activity Diagram (AD) for one Use Case in your system

Dont forget to think about the models with which the AD should match.

8. Develop a sequence diagram (SD) for one Use Case in your system

Dont forget to think about the models with which the SD should match.

9. Develop a State Machine Diagram (SMD) for a Class in your system

You should select an important class. Also, think about what other models the SMD should support.

10. Quality Assurance Statement

Quality Assurance is the activity where you describe the qualifying activities you perform to ensure that your assignment presents models that match each other and offer a cohesive picture of the study/analysis. You need to describe the steps you have taken to ensure that all models matched and added to the story.

11. References

Make sure you cite and write the reference any sources you use. You should be using several sources for this assignment.

Note:

- It must be in the same group of project-1

- You must submit a (word doc) report

- You must prepare PowerPoint slides and present in the lab class.

g

X V Visio Mindset 100 TO