CS 552 JNTU Roles and Skill Sets of Systems v Business Analysts Discussion Questions

User Generated

ngpbbcre61

Computer Science

CS 552

Jawaharlal Nehru Technological University

CS

Description

Unformatted Attachment Preview

Chapter 4: Business Process and Functional Modeling PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Objectives  Understand the process used to identify business processes and use cases.  Understand the process used to create use-case diagrams  Understand the process used to model business processes with activity diagrams.  Understand the rules and style guidelines for activity diagrams.  Understand the process used to create use case descriptions.  Understand the rules and style guidelines for use case descriptions.  Be able to create functional models of business processes using usecase diagrams, activity diagrams, and use case descriptions. PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Introduction  Now begin the process of turning the requirements into functional models  Models are logical; i.e., independent of how they are implemented (manual or computerized)  Develop use-cases from the requirements  Use-case: how a business system interacts with its environment  Includes a diagram and a description to depict the discrete activities that the users perform  Develop activity diagrams from the use-cases  These model the business processes or how a business operates  Used to illustrate the movement of objects (data) between activities PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Business Process Identification With Use-Cases  Elements of Use-Case Diagrams  Actors: users or other interacting systems  Associations: lines to connect actors and use-cases  Interactions, inclusions, extensions or generalizations  Use-case: a major process in the system that gives a benefit to the users  Subject boundary: a named box that depicts the scope of the system  An association relationship: links an actor with the use case(s) with which it interacts PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Business Process Identification With Use-Cases(Cont.)  Elements of Use-Case Diagrams  An include relationship: Represents the inclusion of the functionality of one use case within another  An extend relationship: Represents the extension of the use case to include optional behavior.  A generalization relationship: Represents a specialized use case to a more generalized one. PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Identifying Major Use-Cases  Review the requirements definition  Identify the subject’s boundaries  Identify the primary actors and their goals  Identify the business processes and major use-cases  Carefully review the current set of use-cases  Split or combine some to create the right size  Identify additional use-cases PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Create a Use-Case Diagram  Place & draw the use-cases  Place & draw the actors  Draw the subject boundary  Add the associations PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Example Use-Case Library Book Collection Management System Use Case Diagram PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. BPM With Activity Diagrams  Business processes consist of a number of activities  Activity diagrams depict the sequence of these activities  Diagrams are abstract and describe processes in general  They model behavior independent of objects  Can be used for any type of process PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Activity Diagram Syntax • Action or Activity – Represents action or set of actions • Control Flow – Shows sequence of execution • Initial Node – The beginning of a set of actions • Final Node – Stops all flows in an activity • Decision Node – Represents a test condition PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Elements of an Activity Diagram  Actions & Activities  Something performed for some specific business reason  Named with a verb and a noun (e.g., Get Patient Information)  Activities can be further sub-divided; actions cannot  Object Nodes: represent the flow of information from one activity to another  Control Flows: model execution paths  Object Flows: model the flow of objects  Control Nodes: 7 types PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Control Nodes  Initial node: the beginning of the set of actions/activities  Final-activity node: stops all actions/activities  Final-flow node: stops one execution path but allows others to continue  Decision node: represents a test to determine which path to use to continue (based on a guard condition)  Merge node: rejoins mutually exclusive execution paths  Fork node: separates a single execution path into one or more parallel paths  Join node: rejoins parallel execution paths PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Activity Diagram Symbols PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Sample Activity Diagram PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Swim lanes  Used to assign responsibility to objects or individuals who actually perform the activity  Represents a separation of roles among objects  Can be drawn horizontally or vertically PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Guidelines for Activity Diagrams 1. Set the scope of the activity being modeled 2. Identify the activities; connect them with flows 3. Identify any decisions that must be made 4. Identify potential parallelism in the process 5. Draw the activity diagram PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Creating an Activity Diagram  Choose a business process identified previously  Review the requirements definition and use-case diagram  Review other documentation collected thus far  Identify the set of activities used in the business process  Identify control flows and nodes  Identify the object flows and nodes  Lay out & draw the diagram (minimize crossing lines) PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Use Cases  The primary driver for all UML diagramming techniques  Depicts activities performed by the users  Describe basic functions of the system:  What the user can do  How the system responds  Use cases are building blocks for continued design activities  Each use-case describes 1 and only 1 function PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Types of Use Cases Essential High-level overview of issues essential to understanding required functionality Detailed description of issues essential to understanding required functionality Real Purpose Amount of information Overview Detail High-level overview of a specific set of steps performed on the real system once implemented Detailed description of a specific set of steps performed on the real system once implemented PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Elements of a Use Case Description • Overview: • Name, ID Number, Type, Primary Actor, Brief Description, Importance Level, Stakeholder(s), Trigger(s) • Relationships: • • • • Association: Communication between the use case and the actors Extend: Extends the functionality of a use case Include: Includes another use case Generalization: Allows use cases to support inheritance • Flow of events • Normal flow: the usual set of activities • Sub-flows: decomposed normal flows to simplify the use-case • Alternate or exceptional flows: those not considered the norm • Optional characteristics (complexity, time, etc.) PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Use Case Writing Guidelines 1. Write in the form of subject-verb-direct object 2. Make sure it is clear who the initiator of the step is 3. Write from independent observer’s perspective 4. Write at about the same level of abstraction 5. Ensure the use case has a sensible set of steps 6. Apply the KISS principle liberally. 7. Write repeating instructions after the set of steps to be repeated PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Creating Use-Case Descriptions 1. Pick a high priority use-case and create an overview:  List the primary actor  Determine its type (overview or detail; essential or real)  List all stakeholders and their interests  Determine the level of importance of the use-case  Briefly describe the use-case  List what triggers the use-case  List its relationship to other use-cases 2. Fill in the steps of the normal flow of events required to complete the use-case PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Creating Use-Case Descriptions (cont.) 3. Ensure that the steps listed are not too complicated or long and are consistent in size with other steps 4. Identify and write the alternate or exceptional flows 5. Carefully review the use-case description and confirm that it is correct 6. Iterate over the entire set of steps again PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Example Use-Case Description PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Verifying & Validating a Use-Case  Use-cases must be verified and validated before beginning structural and behavioral modeling  Utilize a walkthrough:  Perform a review of the models and diagrams created so far  Performed by individuals from the development team and the client (very interactive)  Facilitator: schedule and set up the meeting  Presenter: the one who is responsible for the specific representation being reviewed  Recorder (scribe) to take notes and especially to document errors PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Rules for Verification & Validation 1. Ensure one recorded event in the flows of the use-case description for 2. 3. 4. 5. 6. 7. 8. each action/activity on the activity diagram All objects in an activity diagram must be mentioned in an event of the use-case description The sequence of the use-case description should match the sequence in the activity diagram One and only one description for each use-case All actors listed in a use-case description must be shown on the use-case diagram Stakeholders listed in the use-case description may be shown on the usecase diagram (check local policy) All relationships in the use-case description must be depicted on the usecase diagram All diagram-specific rules must be enforced PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Summary  Presented in this chapter:  The identification of business processes using use-case diagrams and descriptions  Modeling business processes with activity diagrams  How to create the documentation of use-cases and use-case descriptions  How to verify and validate the business processes and functional models PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Chapter 3: Requirements Determination PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Learning Objectives • Learn how to create a requirements definition • Learn various requirements analysis techniques • Learn when to use each requirements analysis techniques • Learn how to gather requirements using interviews, JAD sessions, questionnaires, document analysis & observation • Learn various requirements documentation techniques such as concept maps, story cards & task-lists • Understand when to use each requirements-gathering technique • Be able to begin the creation of a system proposal PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Introduction  The systems development process transforms the existing (as is) system into the proposed (to be) system  Requirements determination  The single most critical step of the entire SDLC  Changes can be made easily in this stage  Most (>50%) system failures are due to problems with requirements  The iterative process of OOSAD is effective because:  Small batches of requirements can be identified and implemented incrementally  The system will evolve over time PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Requirements Determination  Purpose: to convert high level business requirements (from the system request) into detailed requirements that can be used as inputs for creating models  What is a requirement?  A statement of what the system must do or a characteristic it must have  Will later evolve into a technical description of how the system will be implemented  Types:  Functional: relates to a process or data  Non-functional: relates to performance or usability PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Requirements Definition  Functional & non-functional requirements listed in outline format  May be prioritized  Provides information needed in subsequent workflows  Defines the scope of the system PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Sample of Requirements Definition PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Determining Requirements  Business & IT personnel need to collaborate  Strategies for problem analysis:  Root cause analysis  Duration analysis  Activity-based costing  Informal benchmarking  Outcome analysis  Technology analysis  Activity elimination PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Determining Requirements  Requirements are best determined by systems analysts and business people together  Techniques for identifying requirements  Interviews, questionnaires and/or observation  Joint application development (JAD)  Document analysis PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Creating a Requirements Definition  Determine the types of functional and non-functional requirements applicable to the project  Use requirements-gathering techniques to collect details  Analysts work with users to verify, change and prioritize each requirement  Continue this process through analysis workflow, but be careful of scope creep  Requirements that meet a need but are not within the current scope can be added to a list of future enhancements PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Problems in Requirements Determination  Analyst may not have access to the correct users  Requirements specifications may be inadequate  Some requirements may not be known in the beginning  Verifying and validating requirements can be difficult PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Requirements Analysis Strategies  Problem analysis  Ask users to identify problems with the current system  Ask users how they would solve these problems  Good for improving efficiency or ease-of-use  Root cause analysis  Focus is on the cause of a problem, not its solution  Create a prioritized list of problems  Try to determine their causes  Once the causes are known, solutions can be developed PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Requirements Analysis Strategies(Cont.)  Duration analysis  Determine the time required to complete each step in a business process  Compare this to the total time required for the entire process  Large differences suggest problems that might be solved by:  Integrating some steps together  Performing some steps simultaneously (in parallel)  Activity-based costing  Same as duration analysis but applied to costs  Informal benchmarking  Analyzes similar processes in other successful organizations PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Requirements Analysis Strategies(Cont.)  Outcome analysis  What does the customer want in the end?  Technology analysis  Apply new technologies to business processes & identify benefits  Activity elimination  Eliminate each activity in a business process in a “force-fit” exercise PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Requirements Gathering Techniques  Process is used to:  Uncover all requirements (those uncovered late in the process are more difficult to incorporate)  Build support and trust among users  Which technique(s) to use?  Interviews  Joint Application Development (JAD)  Questionnaires  Document analysis  Observation PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Interviews  Most popular technique—if you need to know something, just ask  Process:  Select people to interview & create a schedule  Design interview questions (Open-ended, closed-ended, & probing types of questions)  Prepare for the interview (Unstructured vs. structured interview organized in a logical order)  Conduct the interview (Top-down vs. bottom-up)  Follow-up after the interview PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Question Types PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Interviewing Strategies Top-down High-level: Very general How can order processing be improved? How can we reduce the Medium-level: number of times that customers Moderately specific return ordered items? Low-level: Very specific How can we reduce the number of errors in order processing (e.g., shipping the wrong products)? PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Bottom-up Post-Interview  Prepare notes and send to the interviewee for verification PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Joint Application Development (JAD)  Joint user-analyst meeting hosted by a facilitator  10 to 20 users  1 to 2 scribes as needed to record the session  Usually in a specially prepared room  Meetings can be held electronically and anonymously  Reduces problems in group settings  Can be held remotely  Sessions require careful planning to be successful  Users may need to bring documents or user manuals  Ground rules should be established PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Questionnaires  A set of written questions used to obtain information from individuals  May be paper based or electronic (e.g., web based)  Common uses:  Large numbers of people  Need both information and opinions  When designing for use outside the organization (customers, vendors, etc.)  Typical response rates: < 50% (paper); < 30% (Web) PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Questionnaire Steps  Select the participants  Identify the population  Use representative samples for large populations  Designing the questionnaire  Careful question selection  Remove ambiguities  Administering the questionnaire  Working to get good response rate  Offer an incentive (e.g., a free pen)  Questionnaire follow-up  Send results to participants  Send a thank-you PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Good Questionnaire Design  Begin with non-threatening and interesting questions  Group items into logically coherent sections  No important items at the very end  Do not crowd a page with too many items  Avoid abbreviations  Avoid biased or suggestive items or terms  Number questions to avoid confusion  Pretest to identify confusing questions  Provide anonymity to respondents PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Document Analysis  Provides information about the “as-is” system  Review technical documents when available  Review typical user documents:  Forms  Reports  Policy manuals  Look for user additions to forms  Look for unused form elements PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Observation  Users/managers often don’t remember everything they do  Checks validity of information gathered in other ways  Behaviors may change when people are watched  Workers tend to be very careful when watched  Keep a low profile  Try not to interrupt or influence workers  Be careful not to ignore periodic activities  Weekly … Monthly … Annually PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Requirements-Gathering Techniques Compared  A combination of techniques may be used  Document analysis & observation require little training; JAD sessions can be very challenging PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Alternative Techniques  Concept Maps  Represent meaningful relationships between concepts  Focus individuals on a small number of key ideas  User Stories, Story Cards & Task Lists  Associated with agile development methods  Very low tech, high touch, easily updatable, and very portable  Captured using story cards (index cards)  Capture both functional and nonfunctional requirements. PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Story Cards & Task Lists  Capture requirement using story cards (index cards)  File card with single requirement  Each requirement (card) is discussed  How much effort is required to implement it  A task list is created for each requirement (story)  Large requirements can be split into smaller sections  The story can be prioritized by risk level and importance PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. The System Proposal  Combines all material created in planning & analysis  Included sections:  Executive summary  Provides all critical information is summary form  Helps busy executives determine which sections they need to read in more detail  The system request  The workplan  The feasibility analysis  The requirements definition  Current models of the system (expected to evolve) PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. System Proposal Template PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Summary  Presented in this chapter:  Discussion of functional and non-functional requirements determination  Requirements analysis strategies  problem analysis, root cause analysis, duration analysis, activitybased costing analysis, informal benchmarking analysis, outcome analysis, technology analysis and activity elimination  Requirements gathering techniques  Interviews, joint application development, questionnaires, document analysis and observation  Alternative requirements documentation techniques  concept maps, story cards and task lists  The system proposal PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. CS552BH1 OOAD Homework Assignment #1 Fall 2022, Term 1 Rivier University CS552BH1: Object-Oriented Design Homework Assignment #1 Student’s Name: ____________________________________ Please write clearly. Ambiguity will be penalized. Use EXTRA pages if necessary. Copying and pasting answers will also be penalized. You are expected to read and understand the material in the textbook and then answer the questions based on your understanding in your own words. 1. Describe the roles of and activities performed by the Business Analyst and Systems Analyst. 2. Briefly summarize the purpose of the Design Phase in SDLC. Explain why it exists and what it contributes to the completion of the system. 3. Briefly explain what the creators of the Unified Modeling Language (UML) mean by use-case driven, architecture centric, and iterative and incremental. 4. Explain the three different aspects of a feasibility analysis. 5. Plot a Use-Case Diagram for an Online Car Shopping System. Use the Use-Case syntax to draw your diagrams. Page 1|1
Purchase answer to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Explanation & Answer

View attached explanation and answer. Let me know if you have any questions.

1

Outline
Benchmark - Community Organization
Introduction
A community's senior centers are a wonderful resource. They serve as a hub for older people to
access a variety of resources, maintain social connections, and do so. They concentrate on the
often-forgotten elders in the community. Each year, senior centers significantly improve the
quality of life for thousands of local members. And a significant distinction for their adult
offspring, many of whom do not reside nearby. For many participants, maintaining relationships
with others can only be done through their centers. This report details my impressions about the
local senior center based on my observations.
What services are available?


Adult Day Care.



Caregiver Programs.



Case management.

What activities are available for people who come to the center?
1. Group Exercise Classes
2. Wii Sports
3. Walking Clubs.
What does the senior center look like? Is it well-designed as a living space to accommodate
seniors? Explain.
A parking lot stands in front of the sizable structure that houses the senior center. The words
"Senior Center" are written in large characters on a sign. There are several windows throughout
the one-story structure. Outside, there are people moving around and others sitting on seats. The

2

senior center is equipped with broad doors, well-lit rooms, and large halls to make it simple for
seniors to access it. The facility also offers a range of services and activities, including a fitness
center, a library, and a gaming room, to keep seniors active and interested.
How is the senior center funded?
Senior centers need to use resources from multiple sources to keep their doors open. Local
county governments are frequently the main financing sources.
Who administers the programs? Are social workers involved? If so, how?
The largest national membership organization representing senior center personnel is the
National Institute of Senior Centers (NISC).
What are the requirements for who can receive services or participate in activities? Are
there groups that might face challenges accessing center services? If so, explain.
1. prescriptions for medicines and medical care from a doctor.
2. physical examination and medical history.
It is not appropriate for individuals who:
1. Experience profound cognitive impairment
2. Display behavioral signs like roaming
3. Require considerable medical care.
Do you think the center meets the needs and interests of the intended service population?
Explain. If not, what changes could be implemented to better meet needs and interests?
Yes, senior centers are changing to provide what older adults from three different generations
want and need.
Are services designed to build on the strengths and assets of the service population?
Yes

3

Describe a local, state and federal level policy that has an impact on service accessibility
and service delivery for seniors.
The availability of money is a municipal issue that affects senior centers' program delivery and
accessibility. Senior centers could have to reduce services or perhaps shut down if there is not
enough financing. The licensing criteria for senior centers are a state policy that affects service
accessibility and service delivery for senior centers. Senior centers could find it difficult to
comply with the criteria if they are set too high, and they might even have to ...

Similar Content

Related Tags