Details of Assessment
Term and Year Time allowed N/A
Assessment No 2 of 2 Assessment Weighting 50%
Assessment Type Written
Due Date Week 8 Room George St
Details of Subject
Qualification ICT40115 - Certificate IV in Information Technology
Subject Name Systems Analysis
Details of Unit(s) of competency
Unit Code ICTSAD501 Model data objects
ICTSAD502 Model data processes
Details of Student
Student Name
College Student ID
Student Declaration: I declare that the work submitted is my own, and has not been copied or plagiarised from any person or source. Signature: ___________________________
Date: _______/________/_______________
Details of Assessor
Assessor’s Name
Assessment Outcome
Results
0 Competent 0 Not Yet Competent
Marks /50
FEEDBACK TO STUDENT
Progressive feedback to students, identifying gaps in competency and comments on positive improvements:
________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
Student Declaration: I declare that I have been assessed in this unit, and I have been advised of my result. I am also aware of my right to appeal and the reassessment procedure.
Signature: ____________________________
Date: ____/_____/_____
Assessor Declaration: I declare that I have conducted a fair, valid, reliable and flexible assessment with this student, and I have provided appropriate feedback
0 Student did not attend the feedback session.
Feedback provided on assessment.
Signature: ____________________________
Date: ____/_____/_____
Purpose of the Assessment
The purpose of this assessment is to assess the student in the following outcomes: Competent
(C) Not yet Competent
(NYC)
Performance Criteria: ICTSAD501 Model data objects
Element 1. Identify entities and relationships
1.1 Analyse business data to understand operations
1.2 Identify boundaries of the system
1.3 Identify entities, attributes, data types and relationships of data
1.4 Review business rules to determine impact
1.5 Document relationships in an entity relationship diagram
Element 2. Develop normalisation
2.1 Identify suitable business data
2.2 Undertake normalisation of business data and document results
2.3 Compare normalisation results with entity relationship diagram
2.4 Reconcile differences between data
Element 3. Validate model
3.1 Validate data model with client
3.2 Resolve issues or recommendations
3.3 Document completed data model
3.4 Submit to client for final approval
Performance Criteria: ICTSAD502 Model data processes
Element 1. Develop scope of model
1.1 Identify relevant data processes and sources of information
1.2 Identify information gathering method and modelling methodology to be used
1.3 Document modelling information gathered
1.4 Validate modelling information with client
Element 2. Gather process data
2.1 Identify business functions and collect process data using chosen method
2.2 Identify external events, procedures and results
2.3 Identify processes and required decomposition
Element 3. Develop and validate data model
3.1 Model process data according to modelling methodology
3.2 Validate process model with client to determine inaccuracies
3.3 Incorporate identified changes, as required
3.4 Review business rules to determine impact on process models and change as required
3.5 Validate completed process models with client
Assessment/evidence gathering conditions
Each assessment component is recorded as either Competent (C) or Not Yet Competent (NYC). A student can only achieve competence when all assessment components listed under “Purpose of the assessment” section are recorded as competent. Your trainer will give you feedback after the completion of each assessment. A student who is assessed as NYC (Not Yet Competent) is eligible for re-assessment.
Resources required for this assessment
• Computer with relevant software applications and access to internet
• Weekly eLearning notes relevant to the tasks/questions
Instructions for Students
Please read the following instructions carefully
• This assessment has to be completed 1 In class 0 At home
• The assessment is to be completed according to the instructions given by your assessor.
• Feedback on each task will be provided to enable you to determine how your work could be improved. You will be provided with feedback on your work within two weeks of the assessment due date. All other feedback will be provided by the end of the term.
• Should you not answer the questions correctly, you will be given feedback on the results and your gaps in knowledge. You will be given another opportunity to demonstrate your knowledge and skills to be deemed competent for this unit of competency.
• If you are not sure about any aspect of this assessment, please ask for clarification from your assessor.
• Please refer to the College re-assessment for more information (Student handbook).

Assessment – Marking Sheet

TASK DESCRIPTION MARKS
PART A – Entity, Relationship analysis and Normalization

TASK 1: IDENTIFY ENTITIES – NOUN PHRASE ANALYSIS /5
TASK 2: IDENTIFY RELATIONSHIP – VERB ANALYSIS /5
TASK 3: ENTITY RELATIONSHIP DIAGRAM
(validate this with your trainer) /5
TASK 4: PREPARE DATA DICTIONARY FOR ENTITIES
(validate this with your trainer) /10
SUB-TOTAL PART A /25

PART B – Data Flow Diagram and Data Model
TASK 1: IDENTIFY ENTITIES – NOUN PHRASE ANALYSIS
(validate this with your trainer) /5
TASK 2: IDENTIFY RELATIONSHIP – VERB ANALYSIS
(validate this with your trainer) /5
TASK 3: PREPARE DATA DICTIONARY FOR ENTITIES
(validate this with your trainer) /10
TASK 4: ER Diagram and Normalization (2NF/3NF)
(validate this with your trainer) /5
SUB-TOTAL PART B /25

TOTAL /50
Systems Analysis
Assessment 2
Case Study: College Student Registration System (CSRS) and Norman South lift security company


Table of Contents
PART A – Entity, Relationship analysis and Normalization 7
Case Study: College Student Registration System (CSRS) 7
TASK 1: IDENTIFY ENTITIES – NOUN PHRASE ANALYSIS 7
TASK 2: IDENTIFY RELATIONSHIP – VERB ANALYSIS 8
TASK 3: PREPARE DATA DICTIONARY FOR ENTITIES 8
Case Study: Norman South lift security company 9
TASK 4: ER Diagram and Normalization (2NF/3NF) 9
PART B – Data Flow Diagram and Data Model 11
Case Study: College Student Registration System (CSRS) 11
TASK 1: CONTEXT DATA FLOW DIAGRAM 12
TASK 2: LEVEL 0 Data Flow Diagram (DFD) 12
TASK 3: LEVEL 1 Data Flow Diagram (DFD) 13
TASK 4: DATA MODEL and PROCESS MODEL - CRUD MATRIX 14
Appendix 1: Requirements for Drawing DFDs 15
Appendix 2: Documenting DFD Components 17
Process Descriptions 17
Data Dictionary for the Processes in SRS Case 17
External Entity, Data Flow, Data Store and Attribute Definitions 18

PART A – Entity, Relationship analysis and Normalization
Case Study: College Student Registration System (CSRS)
This case study is for Task 1, 2 and 3.
We have been asked to develop an automated College Student Registration Systems (CSRS) for the university. This system will enable students to register on-line for sections each semester. During the registration period preceding each semester, the CSRS will verify whether the student has satisfied the necessary prerequisites for each requested section by referring the student’s on-line transcript of classes completed and grades received. Assuming that (a) the prerequisites for the requested sections are satisfied, and (b) there is room available in each of the sections, the student is enrolled in the sections. Once a section is successfully registered, the system will notify the student. When a section is not registered, either because of prerequisite not verified or room not available, the system will also notify the student.
TASK 1: IDENTIFY ENTITIES – NOUN PHRASE ANALYSIS
Requirements for task
1. Find all nouns.
2. Eliminate duplicates
3. Eliminate references to the system itself.
4. Eliminate references to the organization in question; i.e., the university
5. Eliminate other miscellaneous terms which don’t seem to be entities.
6. Group apparent synonyms, e.g., transcript implies a record of ‘courses completed’ and ‘grades received’.
7. Put aside ‘roles’ of an entity, e.g., a section can have roles of section taken or section is being registered.
Based on College Student Registration System (CSRS) case study and your analysis, please write your resulting entities for the case in here:

TASK 2: IDENTIFY RELATIONSHIP – VERB ANALYSIS
Requirements for task
1. Find the verbs resulting in relationships.
2. Do not include transient actions which do not result in relationships or verbs which are immaterial, e.g., ‘Students track their progress toward completion of their degree’, or ‘Student first enrols at the university’.
Based on College Student Registration System (CSRS) case study and your analysis, please write your resulting relationship matrix for the case in here:
The result is the following matrix:
Entity Relation Matrix Ent1 Ent2 Ent3 Ent4
Ent1
Ent2
Ent3
Ent4
Note: Please use text description to mean a relationship; a check to mean there is a relationship, but naming is not important or possible; a cross to mean no relationship exists.
TASK 3: PREPARE DATA DICTIONARY FOR ENTITIES
PLEASE WRITE YOUR RESULTING ATTRIBUTES OF EACH ENTITIES HERE
Requirements for providing data dictionary for tables:
• Each table needs to have enough attributes to cover the case requirements.
• Identify attribute keys– unique keys, primary keys, foreign keys, composite keys, index keys
• Identify attribute types – data type, user defined types, structured types, reference types and user defined functions
• Describe attribute data types and their application
Based on College Student Registration System (CSRS) case study and your analysis, please write your resulting data dictionary tables for the case in here:
Case Study: Norman South lift security company
This case study is for Task 4.
Norman South is a specialized server room security company. They are not really a very big company. However due to the fact that they have a key technology patented under their company name, they can outsource and contract many staff members over different cities in different countries for their services there.
At this moment, they are receiving their solutions as product packages. However, they are taking order and selling them by email and post. Your company's task is to help them setting up an eCommerce system in their website, so that the selling can be streamlined and done from online via Internet. According to the staff, they will need help with their HR system as well. As this part of the system contains the record of the selling staff over different cities. This part is having a lot of the problems. You studied and found the following record from this part that is having problems.
sales_staff
staff_id sales_person sales_office office_number customer1 customer2 customerr3
1003 David Smith Chicago 312-555-1212 Ford GM
1004 Jennifer Hugh New York 212-555-1212 Dell Apple HP
1005 Frank Chu Chicago 312-555-1212 Boeing
TASK 4: ER Diagram and Normalization (2NF/3NF)
For the Norman South lift security company case study, based on their HR system analysis, please do a normalization on 2NF/3NF level. For assessment 1, you don’t need to do a normalization more than 1NF level.
Based on Norman South lift security HR system case study and your analysis, please list the new tables’ structure, and their ER diagram. For this part, the ER diagram can be drawn both by hand or by a software application.

PART B – Data Flow Diagram and Data Model
Case Study: College Student Registration System (CSRS)
This case study is for all asks of Part B.
We have been asked to develop an automated College Student Registration Systems (CSRS) for the university. This system will enable students to register on-line for sections each semester. During the registration period preceding each semester, the CSRS will verify whether the student has satisfied the necessary prerequisites for each requested section by referring the student’s on-line transcript of classes completed and grades received. Assuming that (a) the prerequisites for the requested sections are satisfied, and (b) there is room available in each of the sections, the student is enrolled in the sections. Once a section is successfully registered, the system will notify the student. When a section is not registered, either because of prerequisite not verified or room not available, the system will also notify the student.
We have been asked to develop an automated College Student Registration Systems (SRS) for the college. This system will enable students to register on-line for sections each semester.
Example DFD Context and Leve-0 is provided below as guidelines to your DFD diagram.

During the registration period preceding each semester, the CSRS will verify whether the student has satisfied the necessary prerequisites for each requested section by referring the student’s on-line transcript of classes completed and grades received. Assuming that (a) the prerequisites for the requested sections are satisfied, and (b) there is room available in each of the sections, the student is enrolled in the sections. Once a section is successfully registered, the system will notify the student. When a section is not registered, either because of prerequisite not verified or room not available, the system will also notify the student.
TASK 1: CONTEXT DATA FLOW DIAGRAM
The Student Registration System contains 5 ‘major’ processes: Verify Prerequisite, Check Room Availability & Add to Waiting List, Notify Enrolment, and Enrol. The system also contains the data flows between the processes and data stores.
Based on College Student Registration System (CSRS) case study and your analysis, please write your resulting context data flow diagram for the case in here:
Drawing Guidelines
• Draw the context diagram so it fits on one page
• Use the name of the information system as the process name in the context diagram
• Use unique names within each set of symbols
• Do not cross lines
• Provide a unique name and reference number for each process
• Obtain user input and feedback
TASK 2: LEVEL 0 Data Flow Diagram (DFD)
The drawing guidelines for level 0 data flow diagram have been provided in class activity, appendices of this assessment and the previous assessment. The DFD may be used for any level of data abstraction. DFD can be partitioned into levels. Each level has more information flow and data functional details than the previous level.
Based on College Student Registration System (CSRS) case study and your analysis, please write your resulting Level 0 data flow diagram for the case in here:
Drawing Guidelines:
• Level 0 DFD must balance with the context diagram it describes.
• Input going into a process are different from outputs leaving the process.
• Data stores are first shown at this level.
• If same data flows in both directions, you can use a double-headed arrow
• Diagram 0 represents exploded view of process 0
• Parent diagram
• Child diagram
• Functional primitive
TASK 3: LEVEL 1 Data Flow Diagram (DFD)
Consider: A Subsystem of ‘check Room Availability’
Following the above CSRS case, the college maintains a waiting list for each section. If prerequisite requirement is satisfied, but room is not available, the student is placed on the first-come, first-served waiting list. If a class/section that she/he was previously wait-listed for becomes available, the first-come student will be automatically added into that section.
In Level 1 of DFD, the processes could be considered as the sub-module(s) of function(s) of the project or module. Further guidelines of this subsystem process is provided in appendices of this document.
Based on College Student Registration System (CSRS) case study and your analysis, please write your resulting Level 1 data flow diagram for the case in here:
Drawing Guidelines:
• Level 1 DFD must balance with the Level 0 it describes.
• Input going into a process are different from outputs leaving the process.
• Continue to show data stores.
• Uses a series of increasingly detailed DFDs to describe an information system
• Exploding, partitioning, or decomposing

TASK 4: DATA MODEL and PROCESS MODEL - CRUD MATRIX
CRUD Matrix is an important Software Design and System Analysis Tool. Crud is a table (can be implemented by a spreadsheet) that for every process in a system defines its interactions with main entities: Create, Read, Update, Delete. CRUD table was used mainly during database design, but I think this technique can be used for every data flow in a system (including external actors and entities). With CRUD matrix, we can see how basic processes interacts with internal data and external entities.
Requirements for CRUD Matrix
A dataflow contains data from entities.
CRUD (create, read, update, delete) matrix highlights data requirement for each process. This table is for SRS example.
Based on College Student Registration System (CSRS) case study and your analysis, please write your resulting CRUD matrix table for the case in here:
Processes, etc E1 E2 E3 E4 E5 E6

E=Entity Name

Appendix 1: Requirements for Drawing DFDs
Example of right and wrong method of DFD


Appendix 2: Documenting DFD Components
(SRS Example)
Each element, including process, data store, and data flow, should be formally defined.
Process Descriptions
1. Each process can be defined by a process decomposition until primitive processes.
2. A primitive can be defined by Structured English
Like programming statements without references to computer concepts.
(a) Rules for structured programming are followed, ex. IF...END IF, DO WHILE (NOT),
(b) Indentation should be used.
Data Dictionary for the Processes in SRS Case
1. Verify Prerequisite
Get registration request
Get Course
Get Transcript
WHILE NOT end of sections requested in the registration request, DO
Check prerequisites in each requested section from Course data store.
WHILE NOT end of prerequisite list, DO
Find the prerequisite in transcript
END DO
IF all prerequisites are in transcript
prerequisite verified for that course/section
Else
Send “registration failure due to prerequisite” to the student for failed sections
End if
END DO
Send registration request with prerequisite verified to ‘Check Room Availability & Add to Waiting List’ process
2. Check Room Availability and Add to Waiting List = 3.1 + 3.2 + 3.3 + 3.4 + 3.5
3. Enroll
Get final registration request from “Check Room Availability & Add to Waiting List”
WHILE NOT end of final registration request
add each enrollment request in the ‘final registration request’ to Enrollment data
store
send ‘availability change’ to Section data store (Update seat available in Section data store)
END DO
Sent enrollment to Enrollment
4. Notify enrollment
Get enrollment from Enrollment
While NOT end of Enrollment, DO
find enrollments of the specified student
END DO
Search the section date, time, course id of each enrollment for the student from Section data store
Send enrollment information to that student
5. Process 3.1 Receive registration request
Receive registration request for the sections whose prerequisites are verified Send the request to Process 3.2
6. Process 3.2 Check room availability
Get registration request from Process 3.1
Get section information from Section data store
WHILE NOT end of sections in the registration request
IF seat available 0
THEN add that section into ‘registered section for that student
(part of final registration request)’
ELSE send ‘failed enrollment’ to ‘Add to waiting list’.
END IF
END DO
Send ‘registered section for that student’ to ‘Enroll
7. Process 3.3 Add to waiting list
Get ‘failed enrollment’ from ‘Check room availability’.
Add that student and section to ‘Waiting list’ data store.
8. Process 3.4 Add wait-listed student
Get sections to see if there is any section becomes available.
WHILE NOT end of all sections
IF seat available 0
THEN get the FCFS (or other rules) student of that section from ‘Waiting list’ data store.
add that student with the section to ‘student and section to be added’.
Send ‘student and section to be added’ to ‘Enroll’.
ELSE return
END IF
END DO
External Entity, Data Flow, Data Store and Attribute Definitions
List all data elements in structured English. Example:
External Entity
Data Store
1. Student
2. Course
3. Section
4. Enrollment
5. Transcript
6. Waiting List
Data Flow
1. student = student id + first name + last name + address + ...
2. section = schedule# + course id + instructor + room + enrollment + seat available
3. waiting_list = section + (student + position) or
waiting_list = schedule# + student_id
4. seat_available = room¬_capacity (an attribute of ROOM) - # of enrollment for that section
5. registered section for that student = registration request with prerequisite verified and room available
6. student and section to be added = wait-listed student when section is available
7. final registration request = registered section for that student + student and section to be added
8. registration request = original registration request, containing all sections requested, from a student
9. registration failure due to prerequisite = notification sent by ‘Verify Prerequisite’ that the course section a student chooses does not meet prerequisite requirement
10. enrollment = student_id + schedule# + date_of_complete + grade
11. transcript = student + enrolment of that student
12. course = course_id + title + credit