COMM391 Section 201 Phase 7

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

1. Non-functional

1.1. real time data

2. Functional

2.1. finding random patterns or trends

3. That is the only way for patients to be able to book appointments on their phone

4. Group 101

4.1. VanRealty - Oracle

4.1.1. FUNCTIONAL

4.1.1.1. Information oriented:We must have information on our customers to see their previous history regarding homes bought/sold, types of properties, preferences, income status/history, location, etc... All confidential of course. We also need to ensure that we have some form of main database that records ifnormation about all of the houses that individual clients are viewing at this time and as well as those who have expressed particular interest in these properties will be viewable to our staff base.

4.1.1.2. Process Oriented: Browse/find data on property listings based on their preferences.

4.1.1.3. With all of this information gained from our information-oriented and process-oriented aspects, we will be able to use this in order to develop patterns and trends (in the form of statistics) to see patters over time as well as predict future forecasts of buyrs and sellers behaviour and past decisions/interest.

4.1.2. NON-FUNCTIONAL

4.1.2.1. Operational: Our website (which have the "search engine", social media, etc. should be viewable on smart phones, ipads, tablets and other forms of technological gadgets.

4.1.2.2. Performance: Our page should take no more than 2-3 seconds to load and when they search for listings or opportunities on our page, it should also not take them more than 4 seconds to load. Other things that we offer on our website such as customer log-in's will be extremely efficient and functioning as fast as possible. This is also the case for when they register for an account on the website

4.1.2.3. Security: Although this does place boundaries on our customer base, only our VanRealty VIP members (this is any user of our registration and login accounts in the database) will have access to our comprehensive database, our personal listings with recommendations, and other information only for VIP members on our websites

4.1.2.4. Cultural, Political, Legal: Our gathering of information whether it's through the methods we use or whether customers enter their own informatino will be kept completely confidential due to privacy laws. We only gain access to their information when the customers give us consent to do so by clicking our "Terms and Agreement " Conditions dcoument and when they click "allow" on our social media, giving us permission to view certian information and take stats for our company use. Although we are granted rights to use this information as permitted by our clients, we do not have a right in any way to sell this information in any form. For all that has been mentinoed above regarding privacy laws and terms & agreement, we ensure that we communicate this to our customers/clients through one of our very disciplined privacy policy

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

6. Group 105

6.1. Good Foods

6.1.1. Product Catalague

6.1.1.1. Functional

6.1.1.1.1. tracking goods (inventory, shelves) like what goes out and in

6.1.1.2. Non- Functional

6.1.1.2.1. be able to update in time

6.1.2. POS System

6.1.2.1. Functional

6.1.2.1.1. scan the product

6.1.2.2. non-functional: be able to recognize our loyalty cards

6.1.3. Data Mining

6.1.3.1. Non-functional

6.1.3.1.1. make sure it shows all the results and does not exclude anything.

6.1.4. RFID

6.1.4.1. Functional

6.1.4.1.1. know the location of our goods

7. Group 106 - DataMed Clinic

7.1. Functional Requirements

7.1.1. Process Oriented

7.1.1.1. Our Database must allow medical staff (doctors and nurses) to access our database of patient records

7.1.1.1.1. Can be accessed through a username/password

7.1.1.1.2. Patients would be able to access their own health history data and availability of appointment times

7.1.2. Information Oriented

7.1.2.1. We must obtain all patient information (age, gender, insurance..and all other relevant data) and medical history

7.1.2.1.1. The medical staff get a quick report of the patient's medical status before they even arrive in the hospital.

7.2. Non-functional Requirements

7.2.1. Operational

7.2.1.1. Database must be accessible by all internet browsers and smartphones

7.2.1.1.1. E.g. The website must be able to fit on a palm (handheld device) to facilitate medical staff's access to information. (ie. they don't need to go to a central computer that contains all the data)

7.2.2. Performance

7.2.2.1. Speed: Internal website showing medical staff schedules should be able to load in 2 seconds

7.2.2.1.1. Patients can be in an urgent state and require immediate medical aid

7.2.2.2. Capacity: Mobile database must have a large capacity so different medical staff can have access and freely navigate the system at the same time without any problems

7.2.2.3. Reliability: contains private material and relies on information to treat patients

7.2.2.3.1. Have a set of backup data so that if the system ever fails the crucial data would not be entirely lost

7.2.3. Security

7.2.3.1. Only medical staff can access the system

7.2.3.1.1. No use for cleaning staff or irrelevant staff to access private information

7.2.3.2. Should implement an anti-virus system to prevent others from hacking into the system and using patient information illegally

7.2.3.3. There will be a hierarchy system where doctors can access all information and doctors in practice can access most information and nurses access limited information

7.2.3.3.1. Can be sorted through their usernames/accounts generated

8. Group 107

8.1. Knowledge Management System

8.1.1. Functional

8.1.1.1. Process oriented

8.1.1.1.1. Our system is able to access and sort through our information regarding employers and employees. After this process, we will be able to set up our simulation followed by specific interviews and job offerings.

8.1.1.2. Information oriented

8.1.1.2.1. Our system must have information on our customers'(the companies that are hiring) requirements for the job they have an opening for.This way we can identify the qualities that best match with potential employees. In addition, the system must have all the information regarding job seekers to complete the process.

8.1.2. Non-Functional

8.1.2.1. Operational

8.1.2.1.1. Need to be fulfilled with appropriate technologies such as laptop computers or desktops

8.1.2.2. Security

8.1.2.2.1. Privacy settings of employers and employees are vital to our systems. We must ensure that their personal information is protected and only viewable by City Workforce staff. This ties in with cultural, political as well as legal factors.

8.1.2.3. Performance

8.1.2.3.1. Since employers are looking for temporary employees, they want the fastest results. Thus our system must ensure the most precise and efficient matching process possible (there should be time frames provided for employees to fill out simulation, the matching process should be instant, etc)

9. Group 116

9.1. DataMed

9.1.1. Non-functional requirements

9.1.1.1. High security: clients' information, including their medical background would be online, our online database needs high security to guard these information from system failure. Also, we should have different levels of security for different members of staff e.g. doctors can see medical history, nurses can schedules and limit the amount of overlap between the two, they can see each other's but not change it.

9.1.1.2. Speed: the system should be fast, should not take a long time for clients to view and access the database

9.1.1.3. Accessibility: We want our doctors to be able to access it wirelessly on their tablets so that they can input client information as they go through their appointments so our database needs to be compatible with this.

9.1.2. Functional

9.1.2.1. Allow database participants to access the information as required.

9.1.2.2. Has to contain and be able to hold variety of customer information: medical records, lifestyle, basic information such as age, gender

9.1.2.3. Has to be able to maintain and organize customer preferences (ex. must be able to schedule appointment times without conflict)

10. Group 117

10.1. CityWorkforce

10.1.1. Functional

10.1.1.1. Workers need to be able to search for positions

10.1.1.2. Companies need to be able to post positions and their requirements

10.1.1.3. System needs to be able to gather information on the various worker's skills and experience

10.1.1.4. System needs to be able to match workers with available positions

10.1.2. Non-Functional

10.1.2.1. Should be able to run on mobile devices

10.1.2.2. Database needs to be set up in a way that there is only one point of data entry (reduce data redundancy)

10.1.2.3. Website should only be accessible by registered workers and companies

10.1.2.4. The system should be available 24/7

11. Group 118

11.1. MoveIT

11.1.1. GPS

11.1.1.1. Non-functional

11.1.1.1.1. Operational

11.1.1.1.2. Performance

11.1.1.1.3. Security

11.1.1.1.4. Legal

11.1.1.2. Functional

11.1.1.2.1. Process-oriented

11.1.1.2.2. Info-oriented

11.1.2. Database

11.1.2.1. Non-functional

11.1.2.1.1. Operational

11.1.2.1.2. Performance

11.1.2.1.3. Security

11.1.2.1.4. Legal

11.1.2.2. Functional

11.1.2.2.1. Process-oriented

11.1.2.2.2. Info-oriented

11.1.3. DSS

11.1.3.1. Functional

11.1.3.1.1. Process oriented

11.1.3.1.2. New node

12. Group 119

12.1. Recommedation Agents

12.1.1. Functional

12.1.1.1. Info: Be able to give clear information on what actions should be taken for customers

12.1.1.2. Info: Needs to obtain purchase histories/patterns, frequency in visits

12.1.1.3. Info: System must provide recommendation in format to present to marketing department for micromarketing

12.1.1.4. Process: Show customer I.D.'s with their search and purchase patterns

12.1.2. Non-Functional

12.1.2.1. Operational: Able to send recommendations to customers through online profile and email

12.1.2.2. Performance: Must be fast enough to load when new page is loaded or immediately after purchases have been made (or perhaps even before final purchase is made)--within a few seconds

12.1.2.2.1. Gives speed enough for customers to add extra items to cart

12.1.2.3. Security: Only members will have access to offers and recommendations

12.1.2.3.1. Promotes people to join membership club

12.1.2.4. Culture,Political, Legal: System must ensure personal information and trends can only be seen by the member

12.1.2.4.1. Will protect from privacy laws as well as customers feeling comfortable giving us information

13. Group 120

13.1. City Workforce

13.1.1. ERP System

13.1.1.1. Functional Requirements

13.1.1.1.1. Process Oriented

13.1.1.1.2. Information Oriented

13.1.1.2. Non-Functional Requirements

13.1.1.2.1. Operational

13.1.1.2.2. Performance

13.1.1.2.3. Security

14. Group 115 - VanRealty (Cloud Computing)

14.1. Functional requirements

14.1.1. process oriented

14.1.1.1. need to be able to retrieve requests to the system (request to view listings and recommendations and link them with the system sending recommendations and listings)

14.1.1.1.1. needs to be able to collect and create a browser profile for clients on the cloud, in order to create a relevant browser profile in order to provide appropriate recommendations of listings

14.1.1.2. System must be able to record browsing/edit history of users from mobile phones and computers (know who's editing what and when for accountability purposes)

14.1.1.3. System has to be able to automatically back itself up and recover these backups (though this will probably be provided by the company providing the cloud computing services)

14.1.2. Information oriented: The system has to be able to take the information from the listings database and gather information about recommendations to clients

14.2. Non-functional requirements

14.2.1. Security: only realtors should be able to access personal, preference (does the client prefer 1-bedroom houses, etc.) and payment information

14.2.1.1. Have different security levels to maintain privacy of data (realtors shouldn't have access to HR/contact info of other realtors but HR should have access to this info). VPN should also be password protected to ensure that only our realtors are accessing the information.

14.2.2. Performance: Recommendations (for potential properties) need to be sent in real time. Should not take more than a few seconds to load files off of cloud and should be able to process new information quickly in order to develop recommendations based on that new information

14.2.3. Operational:cloud should be viewable on smartphones (for realtors out on open houses or client offices) and desktop computers in office. Can connect office and all realtors to a VPN network that allows realtors and management to access the 'office network' from anywhere, and the cloud will be connected to this vpn network

15. Group 114

15.1. DATAMED- medical mobility

15.1.1. Functional: Letting administration, doctors and patients access information about clients at all times.

15.1.1.1. Non-functional: Should be able to function fast, with a maximum of 4 seconds to load clients medical page, and have security with information.

15.1.1.2. Operational --> operate using the IPad, SMS, Cellphone, or laptop

15.1.1.3. Performance --> Have extensive back-up to information; also have a large capacity to allow a large number of clients (a total of 500 clients under DataMed) to access their inforrmation at the same time.

15.1.1.4. Security (cultural/political) --> private and confidential client medical history

15.1.1.5. Have a database that is situated in Canada to follow local laws and protect the private information about clients

15.1.2. Functional: System must have information, like patient heart rate, upcoming check up dates and drugs prescribed, on hand about patients at all times with easy access.

16. Group 113

16.1. VanRealty- connecting previously interested individuals to new listings

16.1.1. Functional

16.1.1.1. The system needs to link email addresses to newly posted listings based on territorial interest

16.1.1.2. Needs to have central database that holds the names of all past open house visitors to keep track of all the houses individual people are looking at and showing interest in. This information needs to be viewable to all agents in VanRealty

16.1.1.3. Develop statistics regarding open house viewing attendance and interest, from an individual open house, to an area, to a period of time.

16.1.2. Non-functional

16.1.2.1. Data needs to be input through a tablet, and viewable through a tablet.

16.1.2.2. Needs to link new listing with interested buyers email addresses within minutes of the new listing being posted on the MLS system

16.1.2.3. Track individuals offers on houses

16.1.2.4. Information needs to be viewable only to VanRealty agents

16.1.2.5. For security,the system should be able to operate without being compromised by hackers/rivals easily, and the method of implementation should not be easy to copy as the system emphasizes mobile use, which includes the ability to remotely wipe the device if lost while during frequent travels around the city

16.1.2.6. Ability to show portions of data from the system to clients. Agents should be able to show sellers rosters of interested buyers and certain opinions (if they believe the house is overpriced)

16.1.2.7. Need to include a information release agreement for people to sign off on including their information in the database

17. Group 112

17.1. MoveIT

17.1.1. Functional

17.1.1.1. Process and Information Oriented: Process includes searching the information needed by employees. Employees should be able to access all previous and current customer data, they should be able to go through sales history and current sales orders. Attached to each sales order should include sales, revenue, cost, this information can be used as the basis of our analysis and also can be used to predict future trends. On the other hand, information oriented is the data itself, you should have complete and accurate information on suppliers, customers, services performed, etc.

17.1.2. Non-functional

17.1.2.1. Example, if we do cloud computing, this system should be viewable in all the browsers and devices that are used by the company (such as smart phones and tablets).

17.1.2.2. Performance: Have queries done within 2 seconds, employees should be able to look up data within a couple of seconds. (especially because the company is small, it should not take a long time to search this information)

17.1.2.3. Security: Administrative employees, this includes everyone working in the head office, should have a unique user ID and password. Each division is able to view the company data, however they are restricted to only being able to input information regarding their roles and divisions. (example: accounting division is only able to put in information regarding accounting but they are able to view information that the finance division puts in, but they cannot edit or make changes)

17.1.2.4. Legal: Since we are located in BC, we should follow the BC Privacy Act/ Law. We should keep customer information secure (where they live, phone number, etc). This should not be released to a third party or exposed as public information.

18. Group 111 (Cloud Computing)

18.1. City Workforce - Collecting and storing data about clients and the employees we provide them to ensure superior/more efficient matching of employees in the future.

18.1.1. Functional Requirements

18.1.1.1. Process Oriented: System must be accessible by employees through our computers, and must be accessible to our clients and the employees we provide them using our clients systems.

18.1.1.2. Information Oriented: Must be a search function that can be accessed by our employees that allows them to search our labour supply database based on employee skills, characteristics and experience.

18.1.1.3. Process/Information Oriented: Must allow our clients to submit evaluations about the employees we provide them with, and must then store that information for later use by our employees.

18.1.2. Non Functional Requirements

18.1.2.1. Security: The system should only be accessible to our employees, our clients, and the employees we provide.

18.1.2.2. Performance: The database should be able to open an individual page in under 4 seconds with up to around 100,000 people using it at once.

18.1.2.3. Performance: The data we have on our labour supply should be up to date so we can always find the most suitable candidate for our clients.

18.1.2.4. Operational: Visibility on smartphones would be an asset, allowing our clients to enter information/fill out satisfaction forms on the go.

18.1.2.5. Security: Our clients shouldn't be able to view our data about our labour supply, nor should our labour supply be able to view the evaluations submitted by their employers.

19. Group 108

19.1. Good Foods Canada

19.1.1. Functional (Hard) Requirements

19.1.1.1. Process Oriented:

19.1.1.1.1. Online Database must be searchable by both internal managers to view trends and external customers to view stock.

19.1.1.1.2. DSS System must be able to agglomerate consumer data and generate coupons that target individual consumers and defined by their general consumption habits.

19.1.1.2. Info-Oriented:

19.1.1.2.1. TPS System MUST be able to track and store purchase information of customers when entered into the system. We have to be able to access our "customer databank" at any given time.

19.1.2. Non-Functional (Soft) Requirements

19.1.2.1. Operational:

19.1.2.1.1. Database must be editable/accessible via checkout registers in order for our employees to effectively make use of the system. Smart phones should easily be able to access our online store

19.1.2.2. Performance:

19.1.2.2.1. The TPS system should be fast enough to use on a daily basis: entering information must be quick and effective in order for customers not to complain about long checkout times

19.1.2.2.2. The database should have the capacity to hold information on all of our customers

19.1.2.2.3. The database should be reliable enough so that it doesn't crash after subsequent use.

19.1.2.3. Security:

19.1.2.3.1. Personal information must be protected from prying eyes and used only for internal use: leaks should be avoided at all costs. Should follow all legal compliances

20. Group 109

20.1. Information- oriented - The information system Moveit uses is DSS. The system allows us to collect and analyze information on customers(such as customers names,addresses, moving routes).

20.2. Operational - For non-functional requirement, we can create an official company website and an appointment bookings app which customers can access on smart phones.

21. Group 110

21.1. Functional Requirements

21.1.1. Process-oriented- Logging reservation information, from there this information will be used to schedule trucks, employees, and other resources. Generating search results regarding fleet location. Tracking returned inventory. Information oriented - The system will the store information on store customers profiles including payment information Customer rewards information Inventory Routes Vehicle information, maintenance

21.2. Non-Functional Requirements

21.2.1. Operations - The mobile application should be compatible with all smartphone platforms so that all users can access information Performance - The GPS system should be robust in reporting accurate locations. Security - All customers data should have restricted access in order to ensure confidentiality. Also credit card numbers should be stored as encrypted rather than in text form to secure privacy.

22. Group 104

22.1. Vanalyst

22.1.1. Functional

22.1.1.1. Process Oriented

22.1.1.1.1. Clients can track his or her investment history through mobile application

22.1.1.2. Informational Oriented

22.1.1.2.1. market information and client portfolios are accessible for analyst at all times

22.1.1.2.2. clients have access to their portfolios through mobile application

22.1.2. Non-Functional

22.1.2.1. portfolios are updated at real-time capital market conditions

22.1.2.2. Performance

22.1.2.2.1. mobile application should load automatically once connected to the internet

22.1.2.2.2. portfolio loaded and can be seen in less than 2 seconds

22.1.2.3. Security

22.1.2.3.1. information are kept confidential and clients can only access portfolios through authorized account

23. Group 103

23.1. Good Foods CANADA

23.1.1. Technology: Online Profile: Gathers customers' nutritional needs, preferences, and is conected to their loyalty card Phone App: Integrate the online profile to in-store use Item Bar-codes: Consumer can scan the bar-codes with their phones to acquire product information

23.1.1.1. Functional

23.1.1.1.1. Process oriented: -must be able to accept user inputs (allergies, vegetarian preferences, etc.) -must be able to filter and match between customer inputs and recipe database -phone app must connect between item bar-code and customer preferences Information oriented: -must have an inventory data base and where items are located in the store -must have nutritional information for all products in the store -must have access to a recipes database which matches items offer in the store

23.1.1.2. Non-functional

23.1.1.2.1. Operational: -our phone app should be able to operate with various OS (apple IOS, android, etc.) -people must be logged into their accounts while scanning products -store price tags must be big enough for bar-codes Performance: -phone app must be constantly update so that it doesn't crash -phone app must be quick when scanning bar-codes: 1-2 seconds -Wifi capacity in the store Security: -customers can't access personal information of other customers -must comply with legal requirements, such as not to sell private customer information Cultural, Political, Legal: -doesn't increase health risks (such as push customers to anorexia) -disclaimer that we are not responsible for individual health problems. -privacy laws (not provide info to third parties

24. Group 102

24.1. VanRealty

24.1.1. Technology: Offer Bidding Service System supported by TPS and DSS (software) that will be provided online

24.1.1.1. Functional:

24.1.1.1.1. Information Oriented (all information kept confidential, only internal use): - system must contain all property listing information - system must contain all realtor information like name, contact information, years of experience - all client information (sellers/buyers) like contact information, name, address, property feature preferences - previous historic bidding prices for each bidder

24.1.1.1.2. Process-Oriented: - system must allow users to browse/search through property listing data - users are able to access all historic bidding prices (specific information regarding bidders will be kept confidential) - system will keep track of user "clicks" on certain property pages and record key features of property that interests user (ie. price range, property feature) in order to create user customization (ie. create customized list of properties that may be in interest to bidders)

24.1.1.2. Non Functional:

24.1.1.2.1. Security: - only realtors belonging to VanRealty's Bidding Service membership will have access to upload their listings in the website and contact bidders - only bidders that registered to bidding membership should be eligible to place bids

24.1.1.2.2. Operation: - website app should be accessible on smart phones - filtered search engine should be available for clients to search properties

24.1.1.2.3. Performance: - due to nature of real time bidding, speed capacity must be reduced to minimum: should not take longer than 5 sec for property listing page to refresh once a new bidding offer is placed

24.1.1.2.4. Cultural/Political/Legal: - realtors within bidding membership will be verified to ensure they are licensed realtors - bidders prior to placing first bid should be verified for credit check (bidding offers will be pending until their credit check is verified) - the system should be offered in Chinese for our target clients to understand information provided on property listing page - privacy issue: all information gathered by the system should be kept strictly confidential, will not be sold to third parties

25. New node

26. New node

27. New node

28. New node