Great Deal! Get Instant $10 FREE in Account on First Order + 10% Cashback on Every Order Order Now

Read the following case study and answer the questions provided below: Case Study: Castleville Council Services Castleville council provides a range of support services and facilities to assist...

1 answer below »
Read the following case study and answer the questions provided below:
Case Study: Castleville Council Services
Castleville council provides a range of support services and facilities to assist individual people and groups in their area to help them lead a happy and comfortable life. The council provides different types of services such as sports services or services related to health, day care facilities or providing services to people who have physical or learning disability. The council is planning to develop a web based system that will make the service management process more efficient for them as well as for the people availing those services.
Summary of Requirements
The proposed system should be able to identify eligible people (client) by individually assessing them according to their need and priority that is decided based on the information entered into the system by social workers or council staff. Some of these services are free of cost for people living in that vicinity however, some services may incur a fee to offset costs and that is related to the person's ability to pay. From time to time, the council can add new services or update or delete existing services.
Castleville council also operates a complaints and representations procedure. People can provide feedback about their experience and services offered to them for future improvements. The system should incorporate this feature as well.
The system should keep a record of individual client details that might include their name, address, contact details, payments made, cu
ent status, allocated social worker etc. There should be a facility for council supervisors to generate administrative reports regarding services provided to different people. There need to be restricted access to any confidential information about clients to those authorised to view the data using a password system
You as a system analyst, are hired by the council authorities, to analyse and design the council services management system that should be able to perform tasks according to the details provided in the above case study. This will also require you to make necessary assumptions and clearly document all your assumptions in your report.
Your report must contain at least the following sections:
· SECTION A: Theory Related Questions
· Introduction: Introduce the important aspects of the case study. (3 marks)
· Work Breakdown Structure: Provide a work
eakdown structure for the given project listing all the steps according to Software Development Life Cycle (SDLC) phases. (5 marks)
· Requirements: List all functional and non-functional requirements as discussed in the case study. (5 marks)
· Information gathering techniques: Identify at least two information gathering techniques that can be used to gather specific requirements and design at least 6 questions that can be asked from relevant stakeholders to capture the system requirements and specifications to develop the system successfully. (3 marks)
· Conclusion: Write a
ief conclusion (Conclusion can be written after competing both sections. (2 marks)
· Structure and Formatting Guidelines (2 marks)
· Add a title/cover page of your choice at the beginning of the report. It should include the name of the assessment, subject name, student’s name, and student ID.
· Insert a table of content next to the title page.
· Insert the page number within the footer of every page in your report.
· Provide appropriate referencing(Harvard-Style) for all academic resources used
· Submit your file using the format: YourNameID_ICT103Exam.docx
SECTION B: Diagram Related Questions    
Based on the outcome of the requirement analysis ca
ied out above, create following diagrams to provide graphical illustration of the proposed system.
· Use Case Diagram: Provide the name and complete description (see Appendix A for description table template) of main use cases for the proposed system and draw a use case diagram. (5 marks)
· Activity Diagram: Provide an activity diagram for any use case identified above (5 marks)
· Entity relationship Diagram : Provide one ER Diagram related to the case study (2.5 marks)
· Domain Model Class Diagram: Provide domain model class diagram for the system (2.5 marks)
· User Interface : Provide a final user interface design using dialog and screen prototypes for any of the use case listed above. (5 marks)
· Test cases: provide a sample test case table with a list of test cases that can be used to test the new system (see Appendix A for test case table template) (5 marks)
· Modelling Diagrams: Clearly define and describe your findings in few words represented by each diagram related to the case study and use accurate technical language, a
eviations and symbols. (5 marks)
Appendix A:
Use case description table: System Name :
Use Case(s)
    Use Case ID:
    Enter a unique numeric identifier for the Use Case. e.g. UC-1
    Use Case Name:
    Enter a short name for the Use Case using an active ve
phrase. e.g. Withdraw Cash
    Created By:
    Enter your name and student ID
    Date Created:
    Enter date of creation
    Actors:
    [An actor is a person or other entity external to the software system being specified who interacts with the system and performs use cases to accomplish tasks. Different actors often co
espond to different user classes, or roles, identified from the customer community that will use the product.
Name the actor that will be initiating this use case (primary) and any other actors who will participate in completing the use case (secondary).]
    Description:
    [Provide a
ief description of the reason for and outcome of this use case.]
    Trigger:
    [Identify the event that initiates the use case. This could be an external business event or system event that causes the use case to begin, or it could be the first step in the normal flow.]
    Preconditions:
    [List any activities that must take place, or any conditions that must be true, before the use case can be started. Number each pre-condition. e.g.
    Postconditions:
    [Describe the state of the system at the conclusion of the use case execution. Should include both minimal guarantees (what must happen even if the actor’s goal is not achieved) and the success guarantees (what
happens when the actor’s goal is achieved. Number each post-condition. e.g.
    Normal Flow:
    [Provide a detailed description of the user actions and system responses that will take place during execution of the use case under normal, expected conditions. This dialog sequence will ultimately lead to accomplishing the goal stated in the use case name and description.
    Alternative Flows: [Alternative Flow 1 – Not in Network]
    [Document legitimate
anches from the main flow to handle special conditions (also known as extensions). For each alternative flow reference the
anching step number of the normal flow and the condition which must be true in order for this extension to be executed. e.g. Alternative flows in the Withdraw Cash transaction:
Note: Insert a new row for each distinctive alternative flow. ]
    Exceptions:
    [Describe any anticipated e
or conditions that could occur during execution of the use case, and define how the system is to respond to those conditions.
    Includes:
    [List any other use cases that are included (“called”) by this use case. Common functionality that appears in multiple use cases can be split out into a separate use case that is included by the ones that need that common functionality. e.g. steps 1-4 in the normal flow would be required for all types
of ticket vending transactions- a Use Case could be written for these steps and “included” in all ticket vending Use Cases.]
    Frequency of Use:
    [How often will this Use Case be executed. This information is primarily useful for designers. e.g. enter values such as 50 per hour, 200 per day, once a week, once a year, on demand etc.]
Test case table: one example provided for idea
    Test Case Id
    Use Case ID
    Short Description
    Test Conditions
    Expected Outcomes
    T101
    U01
    Maintain Client Info
    Add client, Update client, delete not allowed
    New client created
with all fields, Existing client
    
    
    
    
    updated with
    
    
    
    
    selected fields
    T102
    
    
    
    
    T103
    
    
    
    
    T104
    
    
    
    
    T105
    
    
    
    
    T106
Answered Same Day Jun 17, 2021

Solution

Neha answered on Jun 18 2021
148 Votes
60651 - castleville/Acitivity Diagram.png
60651 - castleville/ClientUse Case Diagram.png
60651 - castleville/Customer use Diagram.png
60651 - castleville/ER Diagram.png
60651 - castleville/Section A.docx
Introduction
This report is based on a Castleville council who are well known for helping the individual people or group of people with different types of facilities and support services. They provide these facilities to let these people have a better lifestyle. Sports services, day care facilities, facilities for disabled people, health facilities are provided to the people. These people have to visit the office to request for the service and then the staff members verify the details submitted by the customers which takes a lot of time and resources. The council wants to develop a web-based system which can help them in managing this workflow. the new system can make the work more efficient for both the customers and the staff members.
The new web based system will have a capability to find out the people or client on the basis of their priority and requirements on the individual level full stock the staff members can verify the details provided by the clients and all this information related with the customers like their name, age, address comma id proof will be stored in the database which can be accessed in future. There are few services which are paid and the system will allow the customers to make the payment using the system only . They do not have to visit the office. The system will have a separate process to handle the complaints submitted by customers. The system will allow the council to generate a report for all the services provided to the different customers. The system will ask for the username and password to the user before allowing them to access the system and it will authorise the user.
Work Breakdown Structure
Planning: The very first step of starting a system is the planning step. It is the most important part of the software development life cycle. Senior members of the team will conduct this step and multiple meetings will be done with the sales Department, expert of the industry, market service and the customers. all the information is gathered in this step which is used to plan for the basic approach which can be used to develop the product and it also involves conducting the feasibility study for the technical areas, economical areas and the operational areas of the product . If the planning is perfect then it ensures that there will be minimum or no risk for the project . The feasibility study helps to define the technical approaches which can be followed.
Requirements: once the planning is done then the requirements need to be documented for the project. All the requirements will be written in a document which is known as system requirement specification and it will be approved by the client. The SRS will have the complete requirements of the project which will be developed during the whole life cycle of the system.
Designing: The 3rd stage is to design the system will stop the SRS document will be used to design the product. We can have more than one design approach on the basis of SRS and those designs will be documented in another document which is known as design document specification. The stakeholders will check the DDS and will select a best approach on the basis of risk assessment, budget, time constraint, robustness and the design modularity.
Development: The development stage allows us to develop the project . In this step a programming language is selected and the design presented in DDS is implemented. All the guidelines for the coding will be followed by the developers. The type of code decides the programming language which can be used.
Testing: Testing is another most important step of the sdlc...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here