Member Avatar for ishancoolstar

Diggit, is funded by the local authority in the Greenwich area. The project is to take young people who are seen at risk of offending and involve them in helping to look after the gardens of the elderly. A young person can be referred to the project from a number of different sources. Typically these would be by a school, the youth offending service, the police, or youth clubs. Elderly people with a need for help with their gardens are referred to Diggit also from a number of different sources, e.g. the local authority or a charities working with the elderly.
When a young person is referred a file is opened for that young person and personal details recorded along with details about the referral (why the young person has been referred, who has referred them, any supporting information). At the end of each gardening visit, notes about the young person’s contribution to the project are recorded. If a young person leaves the project then a final assessment of their contribution and progress is entered into the file.
When an elderly person is referred a file is opened in a similar way. Again, personal details about the elderly person a recorded together with details about the referral and about the type of gardening work they require. At the end of each gardening visit, notes about any issues raised by the elderly person or problems with the work undertaken are recorded. Once very month the elderly person is asked to comment on the service they have received by completing a short questionnaire and this is recorded in their file.
There is one full time worker managing the project and 10 volunteers. There are about 30 young people involved in the project at any one time. The young people are arranged in groups of three or four and each group is led by one of the volunteers. The young people are assigned to working with one volunteer as they join the project. Tim, the full time worker for Diggit, works out a rota of volunteers (they normally give up one morning or afternoon to working on the project) and matches the groups to the requests for working in people’s gardens. After a group has worked in someone’s garden, Tim will phone or call round to the person to make sure they are happy. Diggit now have quite a long list elderly people who have their gardens looked after by the project.
The local authority see this as a successful project and are considering investing more money into to allow the employment of another full time worker and providing some more gardening equipment and a van to transport equipment around. However, they want to see data about how the project is running.

![![![i drew a use case for the future system is this correct](/attachments/small/4/ead60fc4921b0cd9a962d405b6cf0f74.jpg "align-left")](/attachments/small/4/ead60fc4921b0cd9a962d405b6cf0f74.jpg "align-left")](/attachments/small/4/ead60fc4921b0cd9a962d405b6cf0f74.jpg "align-left")

usecase.jpg 157.92 KB usecase.jpg 157.92 KB
  • 2 Contributors
  • 1 Reply
  • 335 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by ssj005

Dani AI

Generated

Short critique and next steps — good start, . The sketch captures many actors and flows but needs clearer scope and explicit primary/secondary (happy path / alternate) scenarios so testers and stakeholders can agree what the system must do. asked for those scenarios; below are compact, testable use-case briefs for the three core goals the diagram should show.

Process referral (Primary actor: Referrer or Staff). Trigger: referral received. Preconditions: minimal contact info present. Main success scenario: 1) Staff records referral and creates participant file; 2) system validates required fields and saves file; 3) system issues a participant ID. Secondary scenarios: A — missing info: staff is prompted to supply required fields (back to step 1). B — duplicate referral: system flags possible duplicate and staff merges or rejects.

Arrange visit and assign group (Primary actor: Staff). Trigger: work request from elderly file or volunteer rota ready. Main success scenario: 1) Staff selects request; 2) system shows available volunteer groups; 3) staff assigns group and date; 4) system notifies volunteer lead and records assignment. Secondary scenarios: A — volunteer unavailable: staff reassigns (loop to step 2). B — elderly cancels: assignment is cancelled and slot freed.

Conduct visit and follow-up (Primary actor: Volunteer / Staff). Trigger: scheduled visit occurs. Main success scenario: 1) volunteer completes job and records visit notes; 2) staff reviews notes and records any issues; 3) system logs visit and updates participant files; 4) follow-up call logged. Secondary scenarios: A — incident/complaint during visit: volunteer logs incident, system escalates to staff. B — elderly requests more work: new request created.

Diagram tips: draw a single system boundary, keep use cases as user goals (e.g., "Arrange visit" not "Open file"), mark reusable behavior with <<include>> (e.g., "Update participant file") and exceptional flows with <<extend>> (e.g., "Handle complaint"). For each use case keep: trigger, pre/postconditions, main steps and numbered alternates (reference main-step numbers). Add a reporting use case (“Generate management report”) for the local authority’s data needs and record audit/log entries for privacy and funding validation.

Member Avatar for ssj005

**Need primary secondary scenarions
**

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.