Chicago Chinatown Free Clinic Services and Computer Networks Upgrade Project Plan

FA2020

Table of Contents

Revision History 1 Project Description 3 Customer Information and Inputs 5 General Information to ALL Class Teams 6 Project Information 6 SMART Criteria/Guidelines 7 CPSC 4190 Software Engineering – System Engineer and Development Team Action Items 7 Project Process and Action items 7 Project Documentation Guidelines 8 Project Update Submission Schedules and Guidelines 10 CPSC 4342 Computer Networks Team Action Items 10 Project Process and Action items 10 Project Documentation Guidelines 10 Project Update Submission Schedules and Guidelines 11 CPSC 8820/IT3310 Project Management Team Action Items 12 Project Process and Action items 12 Project Documentation Update Schedules and Guidelines 12

1. Project Description

To support continue increasing needs for Public Health Service, an international company is planning to sponsor a major local public service organization (Chicago Chinatown Community Clinic) office system, equipment and service upgrade.

Chicago Chinatown Community Center/Clinic

Chicago Chinatown Free Community Clinic Events

Your company is in a short list to compete and hope to win a final Web/Application/Database/Computer Networks contract that will be used to support this effort. Since this is a charitable project, the monetary award is 25% below market price, but still can cover and provide 5% of profit margin for your company, but more importantly, this opportunity provide a critical entry point to continue doing business with this international company, your company need to demonstrate the quality of your products and get this account to survive. The customer is requesting that we provide detailed Project Plan, Web Application, relational DB requirements and network proposal documentation, so this info can be reviewed by their team as soon as possible.

The Chicago Chinatown Community Clinic provides free healthcare and medicine for low-income families in the city. Currently all donations, office personnel (i.e., volunteers, doctors, medical personnel …) and patient records are handwritten on paper or in some volunteer’s own computers. It is very inefficient for volunteers to sift through these records when information needs to be added or updated in current filing system.

Additionally, the clinic facility has only two small rooms, thus the space needed to store the physical records become unmanageable.

The current manual system requires numerous paper forms, with data stores spread throughout the clinic management infrastructure or personal computer. Often information (on forms) is incomplete, multiple copies of the same information exist in the clinic and sometimes forms go missing which may lead to inconsistencies in patient data/records.

Your project is to design an office web application and computer network that meet the following requirements.

· A web site and application will allow volunteers to enter and update volunteers/doctor/nurse/patient and other event information.

· All kinds of clinical equipment, medication, and monetary donations are accepted, these donations need to be tracked.

· Several free clinic events will be planed per year, these needs to be tracked as well.

· The web page will direct volunteers to medication assistance found through Rx Assist and Rx Outreach. The web site will also notify volunteers when a patient’s medication assistance eligibility expires.

· A database to store all above information.

· 2 existing small rooms will be modified and become a front desk (1 personal) with waiting areas, and one administration office (4 personal), equipped with 6 PCs, 2 Scanner, 2 printers and internet Phones.

· 7 additional rooms will be added and constructed to support volunteers work room and 6 new services (i.e., General Internal Medicine, Dentist, Xray, Ultrasound, and Blood Test Lab, and Family and Urgent Care Unit), thus need a computer network to support all these needed equipment, up to 30 users for now (expandable to 90 in the future), and shared office equipment and function (e.g., 10 PCs, 5 printers, 5

scanner, 1 file server, 1 file backup server, email server, database server, high speed internet, …etc, and of course, need associated network services).

· The recruiting of professional medical personal and office volunteers is already underway, they believe they will have enough volunteers to staff all these new services and positions. A web info and recruiting process application will become part of regular Clinic web site activities.

· The international company is involved to secure all needed Medical and Lab equipment from different equipment vendors accordingly. If needed, we can work with the clinic representative to recommend more suitable equipment as well. A separate equipment inventory DB is required to support this effort.

With above information, new Chinatown Clinic will be equipped with a Web/Database management system which is designed to replace their existing manual, paper-based system, and personal/private PCs. The new system will enable a better control the following information: donation, patient, volunteers/doctor/nurse, medicines, and pharmaceutical and equipment information. New application system will provide these services in an efficient manner, with the goal of reducing the time and resources currently required for such tasks. The above office functionalities will be supported by a new computer network with internet ethernet and wireless access as well.

Your company will be working with this international company and Chinatown clinic representatives and is responsible to provide project management plan, Web Application DB and computer network requirement and design document in a timely manner.

Appropriate templates should be used, project management plan, requirement and design review will be scheduled accordingly as well. You will have TBD minutes slot for your presentation. The document and presentation materials must be submitted thru Blackboard x weeks (TBD) before scheduled review meeting as well.

2. Customer Information and Inputs

After requirement review and discussion with customers, we will need to follow up to further clarify our requirement specification if any and customer will likely want us to combine it with a more detailed design section within our requirement documentation. Customer provides the following info (Hints: these should be translated and become part of your requirements write-up):

1) Depend on your proposal, a single or multiple database can be used for entire organization (i.e. DB will be used to plan and track ALL events/schedule, donors/amounts, employees/salary, volunteers/time, recipients/services, inventory, and ALL associated activities.

2) The initial free clinic offering (targeted 12/2020) will cover cities around Chicago; the promotion campaign has already started in these areas.

3) It is expected to have 200 customers to visit the web site per week for the first 6 months, so performance/database availability (24/7) is particularly important to the company. Online donation is highly expected when the website is visited.

4) All donations (medicines, service, online credit cards, cash, money order, check,) will be accepted, tracked and receipts provided.

5) Donors can specify where they want their donation be used and will have a login to check their personal donation account/activities.

6) The accuracy and integrity of DB must be maintained, the access of the DB must be secured as well.

7) To ensure the integrity of the database, the company plan to have a weekly routine maintenance run to fix and correct any DB issues. This is scheduled for every Sunday 10PM to 6AM central time. Daily DB maintenance and backup can only be performed between 1AM to 3AM central times.

8) To insure 24/7 donation/service view and access, the customer want to have a duplex system (i.e. mirror systems and can be switched in less then 30 seconds, so all data must be updated in real time and in-sync all the time. To handle fail over case, the system must support at least 30 seconds worth of data in temporary memory space. This is estimated as 500 visitors/users and their transient state info.

9) The Web portal and frond-end Web user interface will be provided by your team, but all the data will be stored and provided by the database. These will be developed using Java for web application; real time MySQL DB access will be written using C and C++. Network and internet bandwidth will need to be considered, thus shall not be a problem for Database access needs.

10) The secured computer network should support at least 20 users but must be able to increase to 60 users and associated equipment.

3. General Information to ALL Class Teams

3.1 Project Information
1) This is a complete project description for Project Management, Software Development, and Computer Network Teams. Each team member should read the description carefully and perform assigned role for your project accordingly.

2) Each team (3-5 members) in CPSC4190 Software Engineering class work as System Engineer and Feature Software Developer for the GUI, Web application, and DB feature development part of the project.

3) Each team in CPSC4342 (3-5 Members) Computer Network class work as Computer Network Planner/Engineer, who will create and design a computer network to support the project

4) Each team in CPSC8820/IT3310 Project Management class work as Project Manager to manage and support work items performed by CPSC4190 (System Engineer and Software Development) and CPSC4342 (Computer Network Engineer) Teams.

5) Each team should work on your document first. Your associated PPT slides should just be a summary of your document. PPT should be limited to 10-15 slides only.

6) Each team should plan to meet and discuss your project at least 2-3 times per week as needed. Note: All teams in each class needs to maintain, update, submit and ready for review a running weekly working status report and/or document review report to their contact/instructor. All report/doc should be submitted on time thru blackboard before noon of scheduled date.

7) Please utilize the sample templates included in the course Black Board “Project Plan Template” section for your project, follow the schedule and submit your project on time accordingly.

· First Slide MS Power Point (PPT) and File Naming Convention

· Project Management Plan,

· Combined Req and Design/Implementation Specification

· Document Review Report

· Team Weekly Status Report

3.2 SMART Criteria/Guidelines
For a clear communication and document purpose, each requirement, design, implementation, task, work items and problem resolution, should use the following SMART criteria as guidelines (https://en.wikipedia.org/wiki/SMART_criteria):

· Specific – target a specific area for improvement.

· Measurable – quantify or at least suggest an indicator of progress.

· Achievable – specify what will be accomplished

· Realistic – state what results can realistically be achieved, given available resources.

· Time-related – specify when the result(s) can be achieved.

4. Software Engineering – System Engineer and Development Team Action Items

4.1 Project Process and Action items
As a Feature Application System Engineer and Development Team, working with your end users, Project Manager and Feature Test teams, study and start up a project development plan that your will be used to present and manage this feature/project.

Investigate, study, and write a combined user interface and database requirement, and design doc to reflect above info, the customer would like to review a more detailed user interface and database requirement and design specification. The database must provide capabilities to support application such as retrieving/adding/deleting/updating all kind of data as needed (e.g., new user data data). System security, data integrity audit, routine backup, fault recovery, system update and other associated business and maintenance

activities must also be considered to support customer’s day-to-day usage and applications.

4.2 Project Documentation Guidelines
Please focus on the following section in requirement document:

a. For section 1 – for our exercise, give high level view of what is this feature try to accomplish.

b. For section 2 – focus on user interface, data model, data information flow, these interface can be used as starting point, but what are those data and what happen to those data as your users move from one state to another state and where are the data come from and go. It will be easier to fill in another subsection once this is done. Example: Need to look at how “customer data” “inventory data” in the

database will be used by web application. e.g., when a customer visits the web site and click the Sales icon: a query is send and retrieve associated part of the database and pass the info to web application for display … etc. Need to consider all different kind of usage, thus different combination of customer data query, security check/blocking, data update, data delete, insert new service data, remove service, etc.

c. For section 3 – This is supposedly the “heart” of the requirement document (e.g., why we call this a “requirement” document. As example shown in the

template, requirement should have the following format, or something like it. As you can also see in the following examples, you should be able to convert your write-up into many, many requirements ( must have at least 50 of them :-).

For each requirement, please use the following SMART criteria as guidelines Also, in general, the users should be able to add, update, or delete any field(s), record(s) or table(s) as needed.

Sample Requirements for your reference only. Also listed in the Combined Requirements and Design Template.

Note: these are samples, to avoid any plagiarism confusion from others, please update them to your unique specification as needed, i.e., please specify what information are needed to support your requirement.

<Unique Company Name –Web Volunteer – 000100 v1> (Your Name)

A Clinic Web page will provide interface to add, update or delete associated volunteer information (e.g., Volunteer ID, First Name, Last name, Email, Cell Phone, service department, specialty, etc (please specify what detailed info

should be added/updated/deleted)

Implementation: Mandatory or Optional depend on the needs.

<Unique Company Name—Web Medical 000300 v1> (Your Name)

A Clinic Web page will provide add, update, or delete medical personnel information (i.e, Name, Specialty, Associate Medical facility, email, regular and emergency contact info, access privilege, Parking location permit, ……. info (please specify what info should be added/updated/deleted here), all DB transaction must be performed in real time.

Implementation: Mandatory or Optional depend on the needs.

<Unique Company Name-Patient DB-000500 v1> (Your Name)

Add, update or delete Patience info, history, and visiting data can only be performed by log-in user with access level 3. See appendix 123 for all access level category and qualification. (note: in general, if it is simple one, include all info as part of this requirement)

Implementation: Mandatory or Optional depend on the needs.

<Unique Company Name-DB Backup-000700 v1.0> (Your Name)

The feature must support an automated, and schedulable daily and weekly DB backup process as specified in Append 124.

Implementation: Mandatory

<Unique Company Name – Inventory DB-000900 v1.0> (Your Name)

The feature must support, track and update all medical equipment and medicine inventory and cost info (Note specify what info will be kept and maintained in this DB).

Implementation: Mandatory or Optional

<Unique Company Name – Security – 001100 v1> (Your Name) User role and security access level must be assigned and updated According to clinic Guideline (see appendix 126).

Implementation: Mandatory or Optional depend on the needs.

d. For design/implementation section in the document, it is up to you how you want to organize this section. It could be one design unit that covers every requirement, or you could have one design unit to cover user setup interface requirements, one for photo database requirements, one for people quote requirements, etc. In

this section, please apply/incorporate as many theories, design process ……etc. as you can and explain why you choose each for your design. Prototype each of your design units as well. Please note that prototype could be pseudo or actual coding as needed. The database(s) constraints, if any, should also be specified in the design

e. Please note that section 1 should lead to section 2, section 2 should lead to section 3, and section 3 should lead to section 4.

4.3 Project Update Submission Schedules and Guidelines
1) The requirement (section 1, 2, 3, 7, 8) document and presentation materials must be submitted thru Blackboard x weeks before the requirement review/presentation date. Please check syllabus/blackboard for details.

2) The Design/Implementation (section 4, 5, 6, 7, 8) document and presentation materials must be submitted thru Blackboard x weeks before the design review/presentation date. Please check syllabus/blackboard for details.

3) Final Project Review and/or Demo (if ready) will be scheduled on the last day of the class.

5. Computer Networks Team Action Items

5.1 Project Process and Action items
As a network planner, consider the needs of Chicago location and works with your end users, propose a network plan to support the following business arrangement:

1) International Management Team and senior engineers in headquarter (in Paris, 1 manager and 1 senior will be full time working with Development, Networks and System Test team.)

2) Development team in GSU University Park, currently 4, but can expand up to 32 team members

3) System Test contract team in Chicago, 3 Team members with a Lab that has over 100 PC with capability to support automated test over 500 Android, 100 iOS phones, and tablets. New PC/mobile devices, and another test equipment are continued to be added when needed. For the class purpose, your team need to only consider the network needs, the Test Automation will be handled by the test team. Please note that the System Test Team will utilize their existing equipment to perform all system testing function, but their existing network will need to be included as part of your network planning and design activities.

4) A common IP communication, email, File, and application server network

5) Each person is equipped with a Laptop, which can be connected thru

· Secured Corporate Internet site,

· Secured Corporate local LAN,

· Secured Corporate Wireless network.

6) For development work and functional testing, each developer is equipped with 1 Android test phone and a Laptop.

5.2 Project Documentation Guidelines
Based on the above project needs, study and start up a computer network project plan that you will be used to support and manage this international project. Mid-term reviews and Final Project Review will be scheduled per syllabus. Please use the combined Network requirement and Design template for your team project.

Note: Please read and follow the same documentation and at least 50 requirements guidelines from above CPSC4190 Software Engineering project description section 4.2.

5.3 Project Update Submission Schedules and Guidelines
1) The requirement (section 1, 2, 3, 7, 8) document and presentation materials must be submitted to their representatives x weeks before the requirement review and presentation date

2) The Design (section 4, 5, 6, 7, 8) document and presentation materials must be submitted to their representatives x weeks before the design review and presentation date.

3) Final Product Review and/or Demo (if ready) will be scheduled on the last day of the class.

For each requirement, please use the following SMART criteria as guidelines.

Sample Requirements for your reference only. Also listed in the Combined Network Requirements and Design Template.

<Unique Company Name –AppServer- 00010 v1> (John Smith)

Each user should be able to access the Software Application Server on each other’s network.

Implementation: Mandatory.

<Unique Company Name-Email-000300 v1> (David Doe)

Each user should be able to send/receive emails from corporate secured mail server.

Implementation: Mandatory or Optional depend on the needs.

<Unique Company Name-FileServer-000500 v1> (Mary Patel)

Each user should be able to save and/or retrieve needed documentation from secured corporate file server.

Implementation: Mandatory

<Unique Company Name-LAN-000700 v1.0> (Your Name)

The local network should provide each user network access (i.e., login, desktop, laptop, phone, printer, etc) to both local LAN and Wireless network.

Implementation: Mandatory

<Unique Company Name-WAN-000900 v1.0> (Your Name)

The local network should provide each user acesss to remote location according to the corporate network setup and throughput guidelines.

Implementation: Mandatory.

<Unique Company Name-IP-001100 v1.0> (Your Name)

The IP network and IP address design should be provided for each location. Implementation: Mandatory.

<Unique Company Name-VideoConf-001500 v1.0> (Your Name)

The project should provide Video Conference service within the network to each location and each user.

Implementation: Optional

6 Project Management Team Action Items

6.1 Project Process and Action items
As a project manager/Project Management Team , working with your end user, management, development, test, and computer network teams, based on the project management principles, study and start up a project plan that your will be used to track, manage and present this feature/project. In general, the above SMART criteria should also be used as general guideline for all your planning and management activities.

6.2 Project Documentation Update Schedules and Guidelines
1) For the 1st draft version, please review and update each section in the template as much as you can, and with the information we have discussed so far in the classroom. It is not necessary to have a full/completed write-up for each section for this version; just write down what your team think should be included in each section as much as you can as. The project plan document and presentation materials must be submitted to their representatives x weeks before the 1st review and presentation date.

2) For the 2nd draft version (build on top of the first review), please review and update each section with the material/information we have discussed in the classroom and what else you think should be included as well. The project plan document and presentation materials must be submitted to their representatives x weeks before the 2nd review and presentation date.

3) Final Project Review and/or Demo (if ready) will be scheduled on the last day of the class.

Chicago Chinatown Free Clinic Services and Computer Networks Upgrade Project Plan

Disclaimer

We Accept

QuickLinks

Contact us