Phase 7 Mindmap

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

1. We need access to the internet in order for us to upload the information, obtained through video interviews, onto the internet.

2. Group 401

2.1. Website Implementation

2.1.1. Functional requirments

2.1.1.1. Customer login identification

2.1.1.1.1. individual customer profiles

2.1.1.1.2. customer information

2.1.1.2. IT system connecting their personal information to our internal data base

2.1.1.2.1. to provide personalized meal ideas

2.1.1.3. product information

2.1.1.3.1. prices

2.1.1.3.2. current products offered in store

2.1.1.3.3. dailydeals

2.1.1.3.4. event updates

2.1.2. Non-functional requirments

2.1.2.1. viewable on smartphones

2.1.2.1.1. easyaccess

2.1.2.2. enough managers to sustain and manage the website

2.1.2.3. efficiency

2.1.2.3.1. speed = fast

2.1.2.4. easyto use and navigate around

2.1.2.4.1. non-tech savy individuals can use the website

2.1.2.4.2. user friendly

2.1.2.5. capacity

2.1.2.5.1. large to provide our clients with all the necessary information: products/prices/health tips/recipes/ forum for clients to communicate with one another

2.1.2.5.2. updated frequently

2.2. Adequate Your considerations are comprehensive but your result looks like working sheet, you should make it more like a conclusion rather than draft.

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

4. Group 405

4.1. City Workforce

4.1.1. Functional Requirements

4.1.1.1. Process-oriented

4.1.1.1.1. The recruitment of employees require a lengthy process

4.1.1.1.2. There are two databases, one for employees and one for employers

4.1.1.1.3. The system must allow employers to have access to the client's reference and other employment information

4.1.1.2. Information-oriented

4.1.1.2.1. The information obtained through video interviews would be uploaded onto our database.

4.1.1.2.2. There are numerous stages in the recruitment and interview process that would help gather information about the employees for City Workforce's database

4.1.1.2.3. clients who are using our services to seek employment must upload their resume to our database in order to complete the application form

4.1.2. Non-Functional Requirements

4.1.2.1. Operational

4.1.2.1.1. Having a physical and a virtual location

4.1.2.2. Performance

4.1.2.2.1. Efficiency

4.1.2.3. Security

4.1.2.3.1. Information in the system must be protected by firewalls to ensure client privacy

4.1.2.4. Legal

4.1.2.4.1. The information obtained must comply with the privacy act as well as other rules and regulations

4.1.2.4.2. Must also comply with other rules and regulations applicable. etc. the patriot act

4.2. Adequate+ Non-Functional Requirements part need more explanation instead of a few words, some points are a little obvious in Functional requirements.

5. Group 406 (City Workforce)

5.1. Functional Requirements

5.1.1. Information oriented: The system must have information from the workers (work experience, resume, references, soft and hard skills), employers (duration of work term, wages, job requirements, number of jobs needed), and our company (matching criteria, payment records, time spent unmatched)

5.1.2. Process oriented: The software needs to scan the information gathered from the TPS from two different databases (employers and workers) and sort through the information with different sets of criteria in a reliable and consistent way that is quick. It also needs to be able to alert the company when an error occurs or when there is a successful job matching created. It also needs to be an intuitive design that allows users to input information directly into the system.

5.2. Adequate+ Your Functional Requirements part is fine, the non-fuctional ones are too general, for instance, you said " our AI system should make decisions faster than those of our competitors", "should provide the most appropriate employee" but no further explanation or description for that.

5.3. Non-Functional Requirements

5.3.1. Operational

5.3.1.1. City Workforce should have team of technicians to maintain the artificial intelligence system we plan to implement.

5.3.1.2. The system should never crash, so that it does not fail to reinforce the value proposition.

5.3.2. Performance

5.3.2.1. Our AI system should make decisions faster than those of our competitors.

5.3.2.2. The system should be able to facilitate and process information on at least 1,000 businesses (clients).

5.3.2.3. The system should provide the most appropriate employee to each job posting in order to ensure an accurate match.

5.3.3. Security

5.3.3.1. Only clients and employees of City Workforce should be able to input data and information into our AI system.

5.3.4. Cultural, Political, and Legal

5.3.4.1. Our system should respect personal information by complying with Canada's privacy laws.

6. Group 407

6.1. Good Food's Mobile E-Commerce IT implementation

6.1.1. Non-Functional Requirements

6.1.1.1. Operational: It should be accessible on all blackberries, androids, and iPhones.

6.1.1.2. Performance: It should be quick, and easy to use.

6.1.1.3. Security: Customers should have their financial information and purchases highly secured and not able to be hacked into.

6.1.1.4. Cultural, Political, and Legal: It'll comply with the patriot act, and other various privacy laws.

6.1.2. Functional Requirements

6.1.2.1. Process-oriented: The system should be able to provide a reliable method to allow customers to purchase food via their cell phones at any time.

6.1.2.2. Information-oriented: With the cash-value system, customers/managers should be able to see their credit history/preferences.

6.2. Adequate: your explanations are all too general and common sense, more details and further information should be explored.

7. Group 416

7.1. Functional

7.1.1. Process Oriented

7.1.1.1. Database system must have a filtering or organizing process that can quickly bring up information on each patient or doctor.

7.1.1.1.1. Patients will be able to review each appointment (before and after, 24 hour availability) through the online database, accessible to each person through unique login.

7.1.2. Information Oriented

7.1.2.1. Develop database system and archive that can effectively and safely store and organize information.

7.1.2.1.1. Must provide each patients' personal information

7.1.2.2. Have a separate database that keeps track on inventory limit and inbound/outbound logistics

7.1.2.2.1. Analyze records, sales history, daily revenue, incoming and outgoing items, medication stock inventory

7.2. Non Functional

7.2.1. Operational

7.2.1.1. There should be a designated room in the clinic for technical and database administration/maintenance

7.2.1.2. Database should be up to date with current technology

7.2.1.2.1. Available on multiple browsers (Firefox, Chrome, Safari) and operating systems/smartphones (iOS, Android, Blackberry), tablets, etc.

7.2.2. Performance

7.2.2.1. Information retrieval and data mining should be quick and easy to access. Information should load in under 2 seconds as the majority of data will appear in text.

7.2.2.2. System must be reliable and stable as losing patient information can be costly both in client revenue/satisfaction as well as legally.

7.2.3. Security

7.2.3.1. Only doctors are allowed to access the information. Patients cannot access other patient/doctor information aside from their own.

7.2.3.1.1. These restrictions can be carried out through unique login for each patient/doctor

7.2.3.2. For inventory database, limited access to clinic managers and employees. Password protected information.

7.2.4. Cultural, Political, and Legal

7.2.4.1. Acquiring information on patients should adhere to local laws

7.2.4.1.1. Patients should only be able to access their own information and not the information of other patients

7.2.4.1.2. Information cannot be sold or shared

8. Group 417

8.1. MoveIT

8.1.1. Functional requirement

8.1.1.1. Process-oriented: Our system should be easy to use, allowing our customers to check their history anytime

8.1.1.1.1. Customers can check their moving time, date, and all other information by typing in a tracking number provided by us.

8.1.1.2. Information-oriented: Customers need to be able to check on their own information such as where they moved from and where are they planning to move.

8.1.1.2.1. We will also have another server just for employees. So, they will be able to check the information from both old and current customers.

8.1.2. Non-functional requirement

8.1.2.1. Operational: Our system should be able to be used on smart phones so our delivery personnel will be able to confirm/access customers information while on the road to or from moving locations.

8.1.2.2. Performance: our system should also not take more than a minute to load so when delivery personnel are accessing info on the road, they can keep deliveries efficient and fast while checking/confirming customers addresses, delivery info, Names and personal info on customers etc.

8.1.2.3. Security: Only trained employees should be able to view data and information as to keep data safe and correctly used and viewed.

8.1.2.4. Cultural, Political and Legal: The way we collect our data for the system must comply with privacy laws of customers info. Must keep all information confidential to our data system and our employees so no personal information is leaked or seen by the public.

8.1.2.4.1. We can't share or sell customer information to other companies for privacy issues.

9. Group 418

9.1. Functional Requirements

9.1.1. Process Oriented

9.1.1.1. We need the mobile computing system to manage the process of the inflow and the out flow of our inventory logistics.

9.1.1.2. The mobile computing system need to keep track of our inventory by monitoring the exact time of the inflow and outflow of inventory and products, which are very important for food industries because all the products are perishable.

9.1.1.3. The mobile computing also keep the whole flow of the inventory work system, keeps track of time of arrival and the amount of inventory we have.

9.1.2. Information Oriented

9.1.2.1. When mobile computing keeps track of the inventory, we can efficiently gather the information about when to accurately allocate our fund in purchasing the products we need and when is the best time to sell those to maximize our profit.

9.1.2.2. The mobile computing system can also keep track and note the information about suppliers, product types and price, and the number of products coming into the inventory.

9.1.2.3. It will also keep track of the amount of each type of products we sell to our customers, and we can use the information gathered by the system to provide valuable information in predicting next year's or season's demand and appropriate price.

9.2. Non-functional Requirements

9.2.1. Operational

9.2.1.1. The system needs to have a stable base architecture which will make it easy to add additional features and applications to the existing system

9.2.2. Performance

9.2.2.1. Mobile computing application should be able to handle a high volume of traffic such as at least 500 customers at any given time

9.2.3. Security

9.2.3.1. Employees should have full access to information if they they are granted permission from someone with higher up authority and have plans to use it in a way that will benefit the company and not violate the privacy laws of our customers. Ex. marketing

9.2.3.2. all customer info will be password protected. Every employee will be given a user name and their own password. To access information, they must enter their username and corresponding password, then the password to access the locked information

9.2.4. Cultural, Political and Legal

9.2.4.1. Give customer full access to their own information, recipes and suggestions. However other customers should have no access to the information of other customers (privacy laws).

10. Group 419

10.1. Functional

10.1.1. Our system would rely heavily on information-oriented material, where we would select candidates on the basis of past work experience, personality through interviews, background checks, references, educational background etc.

10.1.1.1. Through our functional requirements, we would like to minimize our risk of hiring non-suitable or ineffective employees.

10.1.1.1.1. Additionally, we feel that our system must be full-proof and considerably secure. Within our industry, the loss of the database would be detrimental to our company's reputation

10.1.1.1.2. A large source and database of Information is essential to make the right decisions quickly and efficiently.

10.2. Non-functional

10.2.1. The idea behind our non-functional requirement is to minimize the time between matches. This is especially important, when considering the severity of part-time work and short-term contracts

10.2.1.1. We would look to improve the performance aspect of the non-functional requirements. By this, we stress practicality and efficiency over the general aesthetics.

10.2.1.1.1. New node

11. Group 420

11.1. Functional

11.1.1. Process-Oriented

11.1.1.1. Users needs to be able to see the same information that is on the website on their mobile phone. And it should be easy for consumers to use.

11.1.2. Information-Oriented

11.1.2.1. Consumers need to be able to access nutritional information, contact info, store finder and to be able to log into their personal account all in secure manner.

11.1.2.2. Free of Charge

11.2. Non-Functional

11.2.1. Security

11.2.1.1. It is vital that the information collected both on the mobile App and through the user accounts on our website are kept private and only accessible by the individual. Any information that is to be shared needs to be cleared by the individual. And only senior managers can see their personal info, such as address and contact info.

11.2.1.2. The ability to use Location Services to locate the nearest store also needs to be according to code, ensuring that permission is granted by the user and that their location is safe.

11.2.2. Compatibility

11.2.2.1. The Mobile App needs to be compatible with all major Operating Systems such as IOS, Android and Blackberry

11.2.3. Performance

11.2.3.1. Our apps should be able to perform at a sufficient speed and should be able to properly run such functions as a recipe book and ability to log in. And it should ensure that 1000 ( or more) people can use it at the same time.

11.2.3.2. We feel as though the app should take no longer than 3 seconds to load each page, maximum. We would also like users to be able to store up to 1GB of data including Recipes, wish lists and personal information.

12. Group 415

12.1. CITY WORKFORCE

12.1.1. Non functional

12.1.1.1. Operational

12.1.1.1.1. There should be an easy, straight forward interface for contractors to enter their information on-line.

12.1.1.2. Performance

12.1.1.2.1. The system has to have a 99.9% up time with 1% error rate.

12.1.1.3. Security

12.1.1.3.1. Contractors should not be able to access other contractor or employee information, and should only be able to access certain client information.

12.1.1.4. Cultural, Political, Legal

12.1.1.4.1. Information stored in the cloud should not be stored outside of Canada.

12.1.2. Functional

12.1.2.1. Process Oriented

12.1.2.1.1. The system must allow contractors to submit their resume.

12.1.2.2. Information Oriented

12.1.2.2.1. The system must have information concerning contractor work hours and pay.

13. Group 414 - Website (GFC)

13.1. Functional

13.1.1. Process-oriented

13.1.1.1. Customers and management need to be able to access history of past purchases in order to identify trends, manage costs/benefits, determine preferences, offer coupons/discounts

13.1.1.1.1. Should be able to sort and search for specific items based on popularity for management/promo purposes

13.1.1.2. Customers should be able to "login" to their account any time to place online orders

13.1.1.2.1. By logging in management should be able to view their actions - i.e. what they view, what they buy, how long they look through the website, their location with respect to the closest store, their personal profile (male, female, etc.)

13.1.1.3. Customers will be able to sort food based on price, certified/noncertified organic

13.1.1.3.1. Can click link to supplier profile

13.1.1.4. Allow customers to "click" feedback section and write to GFC about what needs improvement, what is working, etc.

13.1.1.4.1. Feedback should be automatically categorized into "positive" or "negative" feedback so management can efficiently address concerns

13.1.2. info - oriented

13.1.2.1. Full list of all items available in store and online only items

13.1.2.1.1. Must include photo, and price at minimum

13.1.2.2. For certified organic foods (those that have actually been CERTIFIED) can have link to supplier's profile with more info on how product is made/harvested and the processes supplier does (this info will be provided by supplier)

13.1.2.2.1. Also emphasize items that are produced locally

13.1.2.3. Havespecials on seasonal items/holiday items

13.2. non functional

13.2.1. Security

13.2.1.1. all credit card information needs to be protected to ensure that customers rights are not violated

13.2.1.1.1. Need to have secure way to purchase items online via credit card/interact that ensures credit card numbers etc. aren't leaked

13.2.2. operational

13.2.2.1. in conjunction with RFID very quick up-to-date info/data available to customers

13.2.2.2. Lay out of website should be very easy to navigate and should be extremely straight forward payment process as to ensure sales without frustrated customers

13.2.2.3. Need to have knowledgeable staff/service provider to address potential site problems quickly

13.2.3. Performance

13.2.3.1. Customers and staff should be able to access info at all times of the day/ night without glitches

13.2.3.2. Should be able to access info within a reasonable timeframe

13.2.3.2.1. i.e. view same day purchases within hours

13.2.3.3. high speed

13.2.4. other

13.2.4.1. Abide by Privacy Laws

13.2.4.2. Pay attention to seasonal fluxes/wants

14. Group 413

14.1. FUNCTIONAL REQUIREMENTS

14.1.1. 1. Process Oriented - Must be able to filter through patients’ medical records through their IDs - Must be able to produce billing and scheduling information - Must be able to search through doctors IDs to find appropriate doctor to treat the patient - Must be able to keep track of prescriptions, surgeries, etc to produce effective follow-up appointments catered to patients 2. Information Oriented - Must have complete and reliable patient health records -Example: allergies, past treatments, medical conditions, etc. - Must allow clients to view pertinent information (scheduled appointments, test results etc.) without sacrificing security - Statistics of business performance to make necessary improvements

14.2. NON-FUNCTIONAL REQUIREMENTS

14.2.1. 1. Operational - every department should have access - the information presented should be concise and relevant to the operation (no clutter and only present the information needed) - different templates for different visit types 2. Performance - speed is important for customer satisfaction (reduce waiting times by generating information quickly) - work with IT to have “check-ups” for software/program updates to maintain efficiency - be able to have a back up location - large computer storage - information should be in a consistent format 3. Security - Only the patient or their doctor should be able to see their medical history - if seeing multiple doctors within clinic, permission for other than family doctor to access patient file - Secure connection between networks within the clinic - anti-virus control, always being diligent about virus detection so all customer and staff information is kept private and secure - intrusion protection 4. Cultural, Political, or Legal - BC Laws and Regulations - Privacy Act - doctor-patient confidentiality -Illegal to sell or distribute patient personal information - Must be careful on who has access to personal information - Would protect our legal integrity, while allowing us to make updates and correct errors -Unalterable draft of each event and entry -Keep a record on who accesses the accounts -Secure lock-out feature -Prevents unauthorized changes -Preventing access to certain features (like medical history) -Example: Front-desk receptionist

14.3. New node

15. Group 412

16. Group 411

16.1. functional requirements

16.1.1. process requirement - the system must sync new listings with housing market websites such as MLS

16.1.2. the system must match up international buyers to our listed properties based on their preferences and the properties` specifications

16.1.2.1. our agents must be able to view this shortlist and the contact information and profiles of the buyers

16.1.3. Information: the system must have international buyer profiles and property listing information

16.1.3.1. In order for the system to do the requirement mentioned in the first bubble, it is crucial for us to have all the relevant information

16.1.4. process requirement - the system must update our agents by SMS and email of new listings

16.2. non-functional requirements

16.2.1. listings should be viewable on smartphones in a user-friendly format

16.2.1.1. As much as we want our listings to be viewable on devices such as smartphones and tablets, if the costs are too high we would rather spend our budget somewhere else as this isn't our primary goal.

16.2.2. system should perform processes instantly when new listings are input

16.2.3. system shouldn`t ever be down for more than 24 hours

16.2.3.1. As we are not a business that heavily relies on this system, it wouldn't make sense to put a large portion of our budget to maintain and backup the system

16.2.4. it should only take a couple of seconds for the system to search for listings under a few parameters (ie. how many rooms, how many bathrooms, location)

16.2.4.1. as more parameters are added in, the system will need to take some time to come up with the specified listings; we hope the system will be able to come up with the listings without users waiting for a long time

17. Group 408

18. Group 409

18.1. DataMed

18.1.1. Electronic Medical Records

18.1.1.1. Functional Requirements

18.1.1.1.1. Ability to search the database of information

18.1.1.2. Non-Functional Requirements

18.1.1.2.1. Security to prevent unauthorized access of information

18.1.1.2.2. Minimal downtime, low maintenance requirements

18.1.1.2.3. Frequent updating of backup server

18.1.2. Online Booking System

18.1.2.1. Functional Requirements

18.1.2.1.1. Ability to book appointments online

18.1.2.1.2. Must allow for input of basic information on patients who book appointments (e.g. patient name, contact information)

18.1.2.2. Non-Functional Requirements

18.1.2.2.1. Accessible through smartphones, tablets, and other devices

18.1.2.2.2. Minimal downtime, low maintenance requirements

18.1.2.2.3. Intuitive system that is easy to navigate (for less tech-savvy patients; seniors)

18.2. Adequate+ All your points are good, however, if you could provide more explanation and detail, that would be much better.

19. Group 410

19.1. Functional Requirements

19.1.1. Process oriented: Must be able to enhance communication between agent and buyers/sellers

19.1.2. Information-oriented: Must have a database service that connects to MLS listings

19.1.3. Must have the capability to display alerts for customers about their offers on properties

19.1.4. The system's data gathering must be secure, and when users submit their information, it must be on a secure webpage.

19.1.5. Process Oriented: The system should be open to both agents and customers to use, and information should limited accordingly, so customers would only have access to listings and their information, and agents would have access to all information on the website

19.2. Non-Functional Requirements

19.2.1. The system should be accessible by any device with internet access

19.2.2. Security: Customer's personal information must be protected from access by anyone other than the agent

19.2.3. Performance: the website should allow customers to input information and search for a listing that applies to them

19.2.4. The website should have both a networking application and also a data gathering application, so if there are any questions about the process, they can first finish providing their information then ask all on the same page

19.3. Adequate+ You can improve your map by adding more detail and explanation, for example " when users submit their information, it must be on a secure webpage", you may describe how to make a webpage secure.

20. Group 404

20.1. Functional Requirements

20.1.1. Basic Client Information database

20.1.1.1. Updated information on a client's portfolio must be able to reach that client in a timely a reliable manner

20.1.1.2. /\ so that when customers have immediate concerns/questions, we have the answers almost instantly without the hassle

20.1.2. Database of previous market closes for stocks/portfolios of interest

20.1.2.1. historical figures, highs/lows to build stock/portfolio prospectus

20.1.2.2. be aware of trend lines indicating potential future growth/risk and adjust investment strategies accordingly

20.1.3. Daily, real-time market updates

20.1.3.1. Via Bloomberg Terminal and Yahoo Finance

20.1.4. Daily updated information on current assets in all operational portfolios

20.1.4.1. Bonds

20.1.4.1.1. new competition in the market? new technological developments, what affects company bonds

20.1.4.2. Common Stock

20.1.4.3. Real Estate

20.1.4.3.1. projected trend is rising, for example

20.1.4.4. RRSPs

20.2. Non-Functional Requirements

20.2.1. Transparency for trading practises auditors

20.2.1.1. Should Dispel allegations of insider trading

20.2.2. Secure transmitting of information to and from clients

20.2.2.1. Encrypted emails and newsletters

20.2.2.2. Should have password protected individual accounts (password set by client)

20.2.2.2.1. protection against fraud, identity theft

20.2.2.3. database security software against viruses, spyware, hackers etc.

20.2.3. Trade regulations and Embargos

20.2.3.1. Foreign Exchange rate manipulation

20.2.3.2. Boycotted Countries

20.2.3.3. foreign/international policies, trade restrictions

20.2.4. contract between client and firm

20.2.4.1. establish clear understanding of risk in investments; everything is clear between both parties - " no surprises"

20.2.4.2. protect our firm's own assets and held liabilities

20.3. Good- Your considerations are very comprehensive, adding more details would be better.

21. Group 403

22. Group 402 - CloudComputing

22.1. Functional Requirements

22.1.1. Process-Oriented

22.1.1.1. The system must have rapid scalability. Being able to change and instantaneously update information (such as vehicles/fleet under operation/vacant, job completion etc) especially during the delivery process is much needed.

22.1.1.2. The system must allow users to see what moving services they haven't used that other customers have.

22.1.1.3. Employees must be able to view and share files on customer data in their home computer, phones etc. The reason why this is a must is because MoveIT currently has a paper-based system located in its HQ. So, to be able to transform its availability for its employees would yield to greater flexibility in handling data.

22.1.1.4. The system must ensure protection of customer information since it is part of their promise to customer to protect their information. However, this is hard to do because we are also at the same time trying to make this information available through many technological mediums (such as iPad, smart phones, home computer) to allow easy acces to MoveIT employees. However, such a risk can be reduced through private cloud installations.

22.1.2. Information-Oriented

22.1.2.1. Overall Customer Profile - Customer ID, Moving ID, Work Progress (Finished, Incomplete or In Progress) must be obtained by employees about to undergo those delivery processes. Customers would also be able to check this information on their account.

22.1.2.2. GPS location information must be obtained to ensure whether on-time delivery (which is MoveIT's promise to its customers) would be obtained

22.1.2.3. Information must also be obtained from customers, seeing who tapped into company promotions & keeping up with company updates and who are frequent visitors to the system. Accordingly, a more fine tuned offer can then be made

22.2. Non-Functional Requirements

22.2.1. Perfomance

22.2.1.1. The system should be quick since instantaneous updates/changes is mentioned as a "must" in the process section. So, as a result a fast updating system is required.

22.2.1.2. The system must have broad network access for its employers and users. Since MoveIT is planning to expand geographically, this would become ever more important.

22.2.2. Operational

22.2.2.1. The system should only be accessible between company employees and MoveIT customers

22.2.2.1.1. Ties in to the security aspect mentioned above.

22.2.2.2. Should have a certain group to manage, develop and maintain all the information in a technological way

22.2.2.2.1. Should make sure all the online resources are correct and available all the time

22.3. Good Very logic and structured map

23. New node