QUESTION
Case Study Assignment – Part 2
This is the second and ongoing component for your case study.
Note well. If you have not written part one of your case study, then you need to do this now as a critical component for your part 2 case study. If this is the case, then you have forfeited the grade for part 1 of your case study.
You should include part 1 (corrected as appropriate) to show your completed work that informs this second part of the study.
Assignment 2 should not exceed 4 or 5 pages. This page count does not include coversheet, diagrams, and your revised assignment part 1.
You may have as many pages of references as required to support your work.
You might treat the list of required assignment components below as a check list.
Omitting one or more of them will have a negative effect on your assignment grades.
Consult the notes you have been taking during lectures and tutorials combined with the research you have been conducting each week to fully understand the lectures.
1. Update Part 1 of the assignment as indicated in assignment feedback
Note your grader’s feedback about you first part of the case study and adjust to suit.
2. Add activities to event/response table.
This is also an addition to your assignment 1 submission
3. Develop a Context Diagram for your system
If you are not clear what a context diagram might be, then revisit the lecture slides from week 5 onwards.
4. Develop a Level 0 Data Flow Diagram (DFD) for your system (top level)
5. Develop lower level DFDs for the core components of your case
Level 1 and perhaps level 2 core components. This is your judgement call.
6. Design and develop a Data Dictionary for your core system to data elements level
7. Develop Process Specifications for the core components of your system
8. Develop an Entity Relationship Diagram (ERD) for your system
At this stage, you are NOT required to attempt normalisation
9. All assumptions/answers to client questions by client representative (tutor or lecturer) must be documented.Just as for the first part of your case study assignment.
10. List of references (Harvard style).
We are looking for evidence of research and reasoning.
SOLUTION
Answers
1. Activities to event/response table.
Event Activities Trigger Source use case Response Destination
Tom and Lisa wants to buy the nursery school and incorporate computer based information system Planning, designing, implementing Purchase and grow business Tom and Lisa Want to Purchase nursery Nursery availability Tom and Lisa
Cooltools is open all 7 days usable Open on all days cooltools Open available cooltools
The hardware store employs 60 full time and part time employees Recruited for improvement employment cooltools employees employment cooltools
The sales figure is expected to grow 90,000 SKUs 5 times per year work process Sales growth cooltools Growth in sales Expected to grow Cooltools
Classes will be handled by Janet handling Late Fridays and early saturdays Tom and Lisa How to use tools Will be organized by cooltools Cooltools
CoolTools has expanded its divisions
Opened new divisions Business expansion
CoolTools
Division
Success
Hardware, building, rental supplies
The Business executives have purchases a large tract of land
development Purchase
Tom and Lisa
Purchases
Appreciated by building contractors
Land
Tom and Lisa hired Janet to organize classes
hiring Classes on how to handle tools
Janet
Hired
Helpful for all employees
Janet
Building contractors suggest their employees to attend Janet’s classes Conducting classes Employee training Janet Coaching classes Helpful Employees
CoolTools have grown as cooltools hardware and building supplies, cooltools rentals and cooltools how to.
Growth of hadrwares 3 various sectors CoolTools Business growth Tom and Lisa’s desire Their expectations are met
Janet has installed general ledger system and employee benefits systems.
Installed ledgers Installation of new application Janet New application Employee accounting system employees
2. Context Diagram for system
A context diagram is a top level (level 0) data flow diagram. It only contains one process node (process 0) that generalizes the function of the entire system in relationship to external entities.
Response
request
Tom, lisa, janet
manages
HR- sub executives (clerks, suppliers, stockers)
3. Level 0 Data Flow Diagram (DFD) for your system (top level)
4. Lower level DFDs for the core components
5. Entity Relationship Diagram (ERD)
One – one
One – many
Many – many
6. Process Specifications for the core components of system
1. Login level
Begin:
If cooltools
Then lisa, tom, janet
Else
End
2. Stakeholders types level
Begin:
Two types
Internal and external stakeholders
Else
Market stakeholders or non-market stakeholders
End
3. Stakeholders level
Begin:
If External stakeholders
Then
Contractors and clients and government
Else
If internal stakeholders
Executives and HR-department and employees
End
4. Employees level
Begin:
If employees=60;
Part time and fulltime
Else
If employees<60
Need to require
End
5. Applications level
coolTools
Begin:
if only hardware, building supplies, rentals
need to improve
else
add nursery business(to apply modern applicaitons)
end.
6. Maintenance level
Begin:
if employees are educated
company will service and get profits
else
need to hire well educated people and improve business
end
7. Design and develop a Data Dictionary for your core system to data elements level
owner::=Tom+Lisa+Janet(key players)
CoolTools ::=Hardware+Building tools
Stakeholders ::=internal|external
Internal stakeholders ::=Executives+HR-departement+Employees
Exernal Stakeholders ::=Contractors+clients+government
training ::= janeth{Friday+saturday}
8. All assumptions/answers to client questions by client representative must be documented.
• Hardware store: A Store which sells hardware items like tools, nails etc
• Home building: Plumber+carpenter+electrician
• Building contractors: workers+contract owner
• Employee: workers+servents+security
• Skillful: Experienced in handling tools
• Lax: The building codes in rural areas are weak and hence carpenters work from foundations to finishing.
• SKU: Stock keeping unit
• HR department: maintain bills, employee details, stock details etc
9. References.
UML Distilled: A Brief Guide to the Standard Object Modeling Language
Martin Fowler, Kendall Scott
Merrill, J.C. (1983) Stakeholder analysis: A systems approach to inquiry, Berkeley: Center for the study, education, and advancement of women.
mindtools (2012) Stakeholder analysis, [Online], Available: http://www.mindtools.com/pages/article/newPPM_07.htm [11 march 2012].
JG55
But you can order it from our service and receive complete high-quality custom paper. Our service offers Information Technology essay sample that was written by professional writer. If you like one, you have an opportunity to buy a similar paper. Any of the academic papers will be written from scratch, according to all customers’ specifications, expectations and highest standards.”
