COMM391 Section 202 Phase 7

Get Started. It's Free
or sign up with your email address
Rocket clouds
COMM391 Section 202 Phase 7 by Mind Map: COMM391 Section 202 Phase 7

1. Information System is accessing medical records from the database that can be easily displayed through a tablet

2. Group 215

2.1. City WorkForce (Information System: Document Management System, Cloud Computing, and Lucene Search Engine)

2.1.1. Functional Requirements

2.1.1.1. Process Oriented

2.1.1.1.1. City WorkForce should be able to search the information (Search Engine - Lucene)

2.1.1.1.2. The system should be accessible to all of our offices throughout Canada (admin / office staff especially)

2.1.1.1.3. Documents should be able to be tranferred between offices and to clients (Cloud Computing)

2.1.1.1.4. Worker profiles must be able to be updated on a regular basis

2.1.1.2. Information Oriented

2.1.1.2.1. Our system needs to be able to store company information (Document Based Management System)

2.1.1.2.2. Documents stored include resumes, work contracts, appraisals, worker profiles, work records and schedules, as well as other administrative documents

2.1.1.2.3. General Accounting department will store documents such as balance sheets, payrolls, worker wages and financial history into the internal system

2.1.2. Non-Functional Requirements

2.1.2.1. Operational

2.1.2.1.1. system should be viewable by all companies computers, and outside computers using a company log-in username and password

2.1.2.2. Performance

2.1.2.2.1. speed and reliability: transfer speed and search speed should be maximized to ensure efficiency

2.1.2.2.2. Our system must be scalable: be able to incorporate new and upcoming documents; design of the system is based on the growth strategy of the company

2.1.2.3. Cultural, Political, and Legal Requirements

2.1.2.3.1. Cultural: System will be available in English and French, the official languages of Canada

2.1.2.3.2. System must abide by provincial laws on privacy, employment equity, worker's compensation, employment insurance, labour laws such as minimum wage requirements

2.1.2.4. Security

2.1.2.4.1. Authority:access to different parts of the system depending on positions held in City WorkForce Access: system accessible by company employees with unique username and passwords

2.1.2.4.2. Confidentiality of contracts and : not shared with entry level employees

3. What are the functional and non-functional requirements of the information system you want to implement in the organization?

4. Group 205

4.1. MoveIT

4.1.1. Tracking System

4.1.1.1. Functional Requirements

4.1.1.1.1. Information: Accurate GPS System that shows exactly where packages are on a map.

4.1.1.1.2. Process: Must allow customers to view where delivers are.

4.1.1.2. Non-Functional Requirements

4.1.1.2.1. Performance: There should be timely updates. As knowing where your package was an hour ago won't be that useful

4.1.1.2.2. Operational: Have tracking viewable on a Smartphone so when customers are on the move at the same time as using MoveIT, they can still check the status of their package

4.1.1.2.3. Security: Make sure there are unique codes so only the right customers can view it

4.1.1.2.4. Legal: Should comply with privacy laws

4.1.2. Internal Employee System

4.1.2.1. Functional Requirements

4.1.2.1.1. Process: Collect information on employees and past moving orders. Allow employees to update their profile. Ability to search employees for availability for shifts. Also able to search through previous orders through a unique moving code

4.1.2.1.2. Information: Employees: date joined, experience, availability Moving orders: customer information, moving details, feedback from customers

4.1.2.2. Non-Functional Requirements

4.1.2.2.1. Security: Password protected as the information in the system are confidential

4.1.2.2.2. Legal: Keep files for a certain period for legal issues

4.1.2.2.3. Performance: Reliable system that's resistant to crashes as all information is stored in there

4.1.2.2.4. Operational: Easy to use interface as the user is probably not a technology expert

5. Group 207

5.1. Functional Requirements

5.1.1. Process-oriented

5.1.1.1. System must allow medical professionals to search through patient's medical records and history

5.1.1.2. Must have a network connection to the database in order to store client information

5.1.1.3. Must be able to update new information, which may include exam results and medication

5.1.2. Information-oriented

5.1.2.1. System must have clients' medical information

5.1.2.2. Must also have information about client's personal, contact information, family contacts, payment information and number of visits

5.1.2.3. Must have information about prescriptions and lab examinations

5.2. Non-Functional Requirements

5.2.1. Operational

5.2.1.1. The system has to be compatible to the tablet, laptops and pc

5.2.2. Performance

5.2.2.1. It should only take 1-3 seconds to upload or download information.

5.2.2.2. Should be able to access information quickly and simultaneously; there should be no lag

5.2.3. Security

5.2.3.1. Medical information should remain confidential; only authorized staff should be able to access for medical use only

5.2.4. Legal

5.2.4.1. Make sure the system abides to all privacy laws and that doctor-patient confidentiality is respected.

5.3. Information System: Electronic Health Record

6. Group 216

7. Group 217

8. Group 218

8.1. E-commerce

8.1.1. Functional Requirements

8.1.1.1. o Ability to host transactions. Customers use online form to fill in their information, which then sends it to our company so we can book required moving specifications.

8.1.1.2. o Scheduling information. Need to have customers pick their desired time to move, as a result we need up to the minute scheduling capabilities so we don’t book two moves for the same truck at the same time.

8.1.2. Non-functional requirements

8.1.2.1. o Aesthetic appeal

8.1.2.2. o Operational: user friendl

8.1.2.3. o Performance

8.1.2.4. o Viewable on smart phones

8.1.2.5. o App friendly

8.1.2.6. o Security

8.2. GPS

8.2.1. Functional

8.2.1.1. o In situations where location is unknown, GPS is instrumental to get drivers from point A to B.

8.2.2. Non-functional

8.2.2.1. o Information orientated – linked to actual location of vehicle and relay information to driver and company. For the purpose of reducing route delivery times by choosing the shortest route. This reduces costs and increases customer satisfaction.

8.2.2.2. o Information – doubles as inventory check to ensure product safety.

8.3. RFID

8.3.1. Functional

8.3.1.1. o Information – keeps inventory of box to ensure item safety and accountability.

8.3.1.2. o Should be able to re-program the chips to add the new inventory list. - Non-functional:

8.3.2. Non-functional

8.3.2.1. Tracks items

9. Group 219

9.1. MOVEIT - Technology: The App that provides a wireless newsletter service to build customer relationships and maintain customer satisfaction after the moving service is provided.

9.1.1. Functional Requirements

9.1.1.1. Process Oriented: Will allow users to obtain information about local restaurants, cafes, schools, community activities in their new neighbourhood. Needs to be able to aggregate data and update itself in order to provide relevant information based on location. Structured by neighbourhood area and kms distances, and user preferences (sort the data)

9.1.1.2. Information Oriented: Names of restaurants, places, etc. that are organized by location, price, community centre hours, links to websites etc.

9.1.2. Non-Functional Requirements

9.1.2.1. Operational

9.1.2.1.1. This technology should be visible by all smartphones, PC and Apple operation systems. Integrates with our website database, so that the transition from moving service to app service is smooth. When customers sign up with moveIT, their information goes into our database, then from the database we can use their information to provide personalized location services through the Application we provide

9.1.2.2. Performance

9.1.2.2.1. The performance should be fast (no more than 3 seconds to load), with easy search functions, accomodate a medium user capacity with room for expansion, and accomodate users interests (through input field)

9.1.2.3. Security

9.1.2.3.1. Access should be granted to our customers only, (Corporate and Residential),

9.1.2.3.2. Make it safe, big issue to consider. We want customers to understand that their info is safe

9.1.2.3.3. Password protection and keeping hackers out!

9.1.2.4. Cultural, Political and Legal

9.1.2.4.1. Comply with privacy laws, tailor to multiple languages (Customers that are immigrating from other countries)

10. Group 220

10.1. DSS System

10.1.1. Functional Requirement -Give the current info about existing properties. -Make routine decisions for managers -Notice managers that there are exceptional decisions to be made -Launch detailed mathematical analysis for managers

10.1.2. Non Functional Requirement -The layout of the database should be user-friendly -Users can obtain analytical information in a second - Users must type password again before making any changes

10.2. Cloud Computing

10.2.1. Functional requırements -Ensure brokers can access all the clients' information anywhere using different OS -Notify users that there is inconsistency in the database -Establish a well developed anti virus and spyware software

10.2.2. Non Functional Requirement -Privacy issues should be well concerned -The system should back up all the data on weekly basis

10.3. TPS system

10.3.1. Functional Requirement -Record transaction details like commission, sales record and the like -Generate a record of all of these weekly clearly

10.3.2. Non Functional Requirement -Operate quickly -Keep the data for 2 years

11. Group 201

11.1. DataMed

11.1.1. Clinic Logistics System - data primarily supplied using RFID.

11.1.1.1. Functional

11.1.1.1.1. Information Oriented

11.1.1.1.2. Process Oriented

11.1.1.2. Non-Functional

11.1.1.2.1. Operational

11.1.1.2.2. Performance

11.1.1.2.3. Security

11.1.1.2.4. Legal

11.1.2. Clinic Information Database

11.1.2.1. Functional

11.1.2.1.1. Information Oriented

11.1.2.1.2. Process Oriented

11.1.2.2. Non-Functional

11.1.2.2.1. Operational

11.1.2.2.2. Performance

11.1.2.2.3. Security

11.1.2.2.4. Legal

12. Group 214

12.1. Vanalyst

12.1.1. Functional Requirements

12.1.1.1. Process Oriented

12.1.1.1.1. Vanalyst's system must allow customers to view their past transactions (credit history) through the mobile application.

12.1.1.1.2. The system must also perform transactions for the client as the mobile applications primary use is to allow the clients to buy and sell stocks right from their smartphones and thus increasing the number of transactions

12.1.1.2. Information oriented

12.1.1.2.1. The system must allow them to search through their current profile or account in order to see how their portfolios are performing and to see whether they need to buy or sell any stocks

12.1.1.2.2. Brokers and management must also be able to view past transactions so they can define their clients preferences and provide suggestions for future purchases

12.1.2. Non-Functional Requirements

12.1.2.1. Operational

12.1.2.1.1. It is critical to our technology that they system work on the iphone, blackberry and android systems as it is a mobile application service

12.1.2.2. Performance

12.1.2.2.1. Vanalyst's mobile application must be able to perform transactions at a fast pace with great reliability

12.1.2.3. Security

12.1.2.3.1. the application will have multiple layers of security in order to ensure the clients confidence and confidentiality through the application

12.1.2.4. Legal

12.1.2.4.1. The mobile application must follow and abide by all Canadian privacy laws

12.1.2.4.2. Must also follow any online banking and security laws

13. Group 213

13.1. Functional Requirements of GFC's Info Systems: ERP

13.1.1. Process Oriented

13.1.1.1. The ERP system that we will be using in GFC, must be able to inform employees and management of inventory levels at all stores, delivery dates for inventory, and other useful information throughout the company (at all three stores) at any time in a user friendly manner.

13.1.1.2. Must be able to use the current TPS system and inventory tracking devices to make for a less expensive, and easier transition.

13.1.1.3. Must be able to access information on their consumers, and market data, that will benefit GFC by better predicting shopping patterns, demands, and marketing initiatives.

13.1.1.4. Must be able to be accessed by all employees, managers and suppliers, must be able to add new employees, and take employees off the user list if they leave the company.

13.1.2. Information Oriented

13.1.2.1. In order to perform the processes that are necessary to continue business, the information system (ERP) must be able to collect the data regarding the inventory at all three stores ( through data warehousing and TPS). This data must be easily converted to usable, readable information. It must be recorded through computer systems, to be able to be accessed by the ERP system. This is feasible, as all shipments are done tracked electronically, as well as transactions.

13.1.2.2. Must be able to read, gather and organize the data that is collected through previously installed technologies in the company ( the inventory management system) to be able to combine data from all different places in one convenient place as ERP promises

13.2. Non-Functional Requirements of GFC's Info Systems: ERP

13.2.1. Operational

13.2.1.1. Should be accessible through check out screens, for customer service representatives and sales clerks, it would be

13.2.1.2. Current employees should be able to adapt to the new system, to be able to use it smoothly and to its full potential. There should be training implemented prior to the information system being introduced in order for the smoothest transition

13.2.2. Performance

13.2.2.1. Should be extremely fast at updating current information, must be constantly updating with any changes that occur in order to get the most valid and useable information.

13.2.3. Security

13.2.3.1. Should be protected from all other companies and competitors in order to maintain competitive advantage. It should be accessible to ALL employees, mangers, and suppliers as they should all be able to take initiative and be fully informed about the company and feel useful. Perhaps the use of a employee card or password in order to access the information can be used to access the system.

13.2.4. Cultural, Politcal, Legal

13.2.4.1. Given we import a majority of our goods from the United States, it is important that we insure that the system follows all regulations regarding access to any information stored on the system. It will be important to maintain privacy of our employees whose information will most likely be stored on the system. This is something we will have to look into and consider in great detail. If we use a company such as SAP they will be able to provide us with guidance as to how to protect ourselves given the differing privacy laws in USA and Canada

14. Group 212

14.1. MoveIT: technology: Recommendation Agents

14.1.1. Functional Requirements

14.1.1.1. Process oriented

14.1.1.1.1. Customers should be able to access their previous order history, date on which it occurred, and items that were moved.This will help attract repeat customer- especially students who move often and have similar needs

14.1.1.1.2. Customers should be able to update their online profile.

14.1.1.1.3. Customers should be able to indicate their approximate budget by selecting fromm different ranges of budgets (ex. $400-$500, $500-$700 etc). XCustomers should also be able to indicate the date they need to have move completed by

14.1.1.1.4. The system needs to be able to aggregate information on local restaurants etc. from various sources (ex. review websites like Urbanspoon) and should be able to update itself to reflect current information

14.1.1.2. Information-oriented

14.1.1.2.1. The system must obtain information on the local restaurants, amenities (doctors, schools, etc) near the customer's new house so that the company can suggest location-specific information to it's customers

14.1.1.2.2. The system needs to gather information on the customer's restaurant preferences (ex. the type of food the customer likes to eat, the preferred price range), grocery store stype preferences (organic) so that the recommendation agent can make personalized suggestions about location-specific ammenities

14.1.1.2.3. The system needs information on the company's equipment (trucks) abd employees (number, specific training they have received), and associated costs so that that MoveIT can provide and estimated cost and completion time to its customers

14.1.2. Non-functional requirements

14.1.2.1. Security: only employees and customers should be allowed access to customer data

14.1.2.2. Legal: customer's personal information (ex. their current and new house address) should comply with Canadian privacy laws

14.1.2.3. Operational: the website should be viewable on smart phones, allowing customers to access information on local ammenities more portably

14.1.2.4. Performance: all applications should be high speed and be able to handle large capacities of data and provide immediate reccomendations

15. Group 211

15.1. This week's mindmap is dedicated to our teammate who is not in class today. May he Rest in Bed as he obviously overslept *Update! He's in Hawaii

15.1.1. GoodFoods

15.1.1.1. IT: QR Codes

15.1.1.1.1. Functional Requirements

15.1.1.1.2. Non-Functional Requirements

16. Group 208

16.1. Good Foods - use of loyalty program

16.1.1. Functional

16.1.1.1. process oriented

16.1.1.1.1. transmit data into database about customer information/points/purchases

16.1.1.1.2. provide customers with points data

16.1.1.2. information oriented

16.1.1.2.1. points per product

16.1.1.2.2. Information on customers

16.1.2. Non functional

16.1.2.1. Operational

16.1.2.1.1. Mobile app

16.1.2.1.2. Access of info. on website

16.1.2.2. Performance

16.1.2.2.1. Mobile app

16.1.2.3. Security

16.1.2.3.1. Customers' credit card info security

16.1.2.3.2. Limit access to customers' personal information to customers and authorized employees

16.1.2.3.3. Prevent people from hacking and changing point information

16.1.2.4. Cultural, Political, Legal

16.1.2.4.1. Apple regulations for apps

16.1.2.4.2. Information collection must comply with privacy laws

16.1.2.4.3. Storage of credit card information must be legal

16.1.2.4.4. How people feel about personal information privacy, what information they feel comfortable with providing.

16.1.2.4.5. Must comply with laws about point retention

16.1.2.4.6. Cultural acceptance of mobile purchasing

17. Group 209

17.1. City Workforce

17.1.1. Functional Requirements

17.1.1.1. Optimal matching

17.1.1.1.1. The system must match each new job with the most suitable temp who is available at the time.

17.1.1.1.2. The system's recommendation system must learn how to match temps with job openings more effectively (based on new satisfaction ratings and user information).

17.1.1.2. Yield management

17.1.1.2.1. The system must be able to predict periods of low demand for certain temps, and automatically adjust hourly rates for temps in those sectors.

17.1.1.3. Notifications

17.1.1.3.1. System must send form email updates to all affected parties each time a labour request is made or altered

17.1.1.4. Online signup/ Temp request

17.1.1.4.1. Temps and employers must be able to register with City Workforce online, and must be able to update their information online.

17.1.1.4.2. Temps must be able to update their education, skills, interests, preferences, and hours of availability online.

17.1.1.4.3. Employers must be able to request temp workers online.

17.1.1.5. Accounting/Payroll

17.1.1.5.1. Our system must be compatible with our accounting software so that it can extract payroll data based on hours worked, employer charge out rates, and temp hourly wages

17.1.2. Non-Functional Requirements

17.1.2.1. Data should be backed up off-site.

17.1.2.2. Security/Legal

17.1.2.2.1. Data must be securely stored to protect the privacy of employers and temps.

17.1.2.3. Ease-of-use/Accessibility

17.1.2.3.1. Site should be accessible from any browser mobile or not, and be fully compatible with any screen resolution

17.1.2.3.2. The booking software that City Workforce staff use should be intuitive and easy-to-use.

17.1.2.3.3. Online registration system should be easy for empoyers and temp workers to use.

18. Group 210

18.1. Good Foods

18.1.1. Functional

18.1.1.1. Process oriented

18.1.1.1.1. Products must be tagged

18.1.1.1.2. Tags must be distinguishable to provide unique identification

18.1.1.1.3. Tags must allow the RFID scanners to identify the product and update inventory as purchases are made

18.1.1.2. Information oriented

18.1.1.2.1. Keep track of routine transactions and inflow/outflow of inventory

18.1.2. Non functional

18.1.2.1. Operational

18.1.2.1.1. Data capture and inventory counting should be automatic

18.1.2.1.2. RFID readers must be able to detect several RFID tags simultaneously

18.1.2.2. Performance

18.1.2.2.1. Data collected should be transferred automatically to online database

18.1.2.3. Security

18.1.2.3.1. Only authorized personnel should have access to information collected by RFID system

18.1.2.3.2. Have back up operations for database which should be done once a week

18.1.2.4. Cultural/political/legal

18.1.2.4.1. The RFID system's data gathering should comply with privacy laws

19. Group 204

19.1. City Workforce

19.1.1. Networked Collective Intelligence

19.1.1.1. Functional

19.1.1.1.1. Process-Oriented

19.1.1.1.2. Information-Oriented

19.1.1.2. Non-Functional

19.1.1.2.1. Operational

19.1.1.2.2. Performance

19.1.1.2.3. Security

19.1.1.2.4. Legal

19.1.2. Recommendation Agents

20. Group 203

20.1. Van Realty

20.1.1. Employee Performance Management

20.1.1.1. Functional Requirements

20.1.1.1.1. Process Oriented: Must allow our management team to search up agents and be able to see their performance track record. Must also allow our agents to search up a client and view the records of their screening process.

20.1.1.1.2. Information Oriented: System must obtain information on our agents and progress. System must obtain information on our clients. System must obtain information on our listing products

20.1.1.1.3. Process Oriented: System must analyze and share performance related information data for informed decision making.

20.1.1.1.4. System needs to align compensation factors, and performance with comapny goals, and make this clear in it's interface.

20.1.1.2. Non-Functional Requirements

20.1.1.2.1. Security: Full access to information and company records should be only available to management. HRM adminstrator must have full control of individual employee reviews.

20.1.1.2.2. Operational: Our company website should be viewable by smart phones and web browsers (mozilla, IE, Chrome...). Our system should be accessible by all platforms (macs, PCs). The system should provide limited access to clients, limited access to agents,but full access management.

20.1.1.2.3. Performance: Our system definitely needs to be reliable, such that management can consistently and routinely track down the progress of our agents. System needs to be reliable for agents to access client information for reference to better customize service. System needs to be accessible for agents to update client information. The system needs to have a large capacity for data warehousing.

20.1.1.2.4. Cultural: The system should be user friendly, easy to access and be used with no hassles by management and agents alike.

21. Group 202

21.1. Knowledge Management Software and Info. Structure for City Workforce

21.1.1. Functional requirements

21.1.1.1. Process-oriented

21.1.1.1.1. The system must facilitate Associate supervisors to search through job descriptions, assignment duration, and availability of associates in the required specialization for assignments as they arise in order to to match associates and assignments in an efficient manner.

21.1.1.1.2. Must be able to allow management to access information on industry hiring trends, employment data and projections to allocate resources and conduct strategic planning.

21.1.1.1.3. Must be able to give able to integrate with current TPS system of assignment and associate tracking to ease the transition into the new system.

21.1.1.1.4. Must be capable of transfering information on personnel needs from business clients from the Relationship Managers to Associate Supervisors

21.1.1.1.5. Must be able to change the setting of the system add and remove employees from the list of employees who can access the levels of information as they are promoted or leave the organization. the list of employee

21.1.1.2. Information-oriented

21.1.1.2.1. Must have information on job requirements, associate and client profiles, contract terms and durations, associate and employer evaluations.

21.1.1.2.2. Must be able to collect data from existing internal databases and external sources like industry market research and government releases.

21.1.1.2.3. Must be able to convert the information into a user friendly form, varies depending on whether it is to be viewed by associates, supervisors or relations managers.

21.1.2. Non-functional requirements

21.1.2.1. Operational

21.1.2.1.1. Should be available on a variety of interfaces such as traditional desktops, smartphones, tablets and other mobile devices in order to guarantee the immediacy this will help our company give immediate services.

21.1.2.2. Performance

21.1.2.2.1. Applications and online resources need to be able to load quickly and without disruptions and they should be compatible with all the commonly used web browsers as information turnover must be immediate to ensure all the information remain relevant.

21.1.2.2.2. All applications should be at high speed and be able to handle large capacities of info. to allow our company to fulfill the need for immediate service

21.1.2.3. Security

21.1.2.3.1. There should be a restricted access so assignment postings can only be available to associates that have signed a contract with us.

21.1.2.3.2. Should have sufficient security against potential impeachments from competitors or clients' competitors to protect the company's and the client's interests.

21.1.2.4. Legal

21.1.2.4.1. Keep legal and contractual information between our company and client private; also keep legal and contractual information between our company and associates private; maintain non-disclosure agreements.

22. New node

23. Group 206

23.1. VAnalyst

23.1.1. OUR FIRST MAP WAS DELETED AT FIRST

23.1.2. Portfolio Database

23.1.2.1. Functional Requirements

23.1.2.1.1. Process Oriented

23.1.2.1.2. Information Oriented

23.1.2.2. Non-Functional Requirements

23.1.2.2.1. Performance

23.1.2.2.2. Security

23.1.2.2.3. Legal

23.1.2.2.4. Operational

24. New node

25. New node

26. New node