1. Group 318
1.1. Biometric Scanners for physician log in
1.1.1. A PC system compatible with biometric technology
1.1.2. Biometric security software
1.1.3. biometric scanners
1.1.4. Finances to implement system
1.1.4.1. Favorable cost benefit analysis
1.2. HID Key Cards
1.2.1. Pc system
1.2.2. Hid Cards
1.2.3. System to make cards
1.2.4. HID card readers
1.2.5. Software to coordinate cards with required accesses
1.2.6. Very expensive, can use keys, doesn't add value to our business
1.3. Speech to text
1.3.1. A microphone (preferably using bluetooth)
1.3.2. computer system
1.3.3. advanced speech recogntion software that interfaces with our charting system
1.3.4. Technology is more widely available, need to do cost benefit analysis
1.4. Barcode Scanning System
1.4.1. PC system
1.4.2. Barcode creating software
1.4.3. Barcode scanners
1.4.4. Database
1.4.5. Inventory management software to interface with collected scan data
1.4.6. Barcode systems are common and less expensive than alternatives such as rfid tags
1.5. Written Recognition
1.5.1. PC system
1.5.2. written recognition hardware (pen and pad)
1.5.3. Software system to input handwriting, analyze and connect to the appropriate patient charts
1.5.4. Technology is more widely available, need to do cost benefit analysis
1.6. Jonokomed
1.6.1. PC System
1.6.1.1. Every doctor will require a laptop
1.6.1.2. We will need a wireless network
1.6.2. The software
1.6.3. Systems to interface with our technologies and other programs like pharmanet
1.6.4. Storage requriements
1.6.4.1. Data will need to be stored securely on site and backed up off site
2. Group 319
2.1. ERP
2.1.1. Functional
2.1.1.1. Accurately retrieve information Has to have an automated backup and recovery system; this can likely be provided by the cloud service provider though we should have a local backup Automatically manage payroll and generate cheques/direct deposit
2.1.1.2. Reports for CEO: customer satisfaction, making success, monthly/quarterly/yearly, accounting (rev and cost) per customer, analyze costs and profits Reports for Hiring Directors: employee tracking, satisfaction of clients, sales pipeline, potential candidates for open position
2.1.1.3. Forms: input data from the websites for clients as well as employee-side form; candidates must be able to update their profiles
2.1.1.4. Information-oriented
2.1.1.4.1. Make sure that all staff are seeing the same information
2.1.1.4.2. Ensure that it has web platform for clients to access their information
2.1.1.5. Process-oriented
2.1.1.5.1. Connect job-profiles, candidate profiles, etc. to achieve matching
2.1.2. Non-functional
2.1.2.1. Have it accessible from mobile devices Must maintain security of client data; there are likely legal constraints around this
2.1.2.1.1. Different security levels and users to maintain data security and a customer privacy; achieve this through different authority levels of users Must have a secure and constant connection; have to consider going with a LAN rather than a wifi
3. Group 320
3.1. RFID
3.1.1. Functional requirements
3.1.1.1. Information oriented- we must obtain information regarding instock products
3.1.1.2. must be cost effective in order to improve the supply chain
3.1.2. non-functional
3.1.2.1. performance- should take no longer than a few seconds
3.2. ECommerce
3.2.1. Functional requirements
3.2.1.1. - system must record the sales and transaction history of its users
3.2.1.2. - system must show detailed information regarding our products, and allow users to order these products
3.2.1.3. Must have access to online banking services to pay for products
3.2.2. Non-functional
3.2.2.1. Security- subscription uses should have access to recipies while everyone can access the catalogue
3.3. Recommendation agents
3.3.1. non-functional
3.3.1.1. the data we collect and use the users must agree on the use of the information
3.3.2. functional
3.3.2.1. need information from data mining to come up with cross-selling solutions that we can send through newsletters to the cx - not accessing all the databases, just the database concerning cx info
3.4. computer terminals
3.4.1. Functional requirements
3.4.1.1. Needs to detect the bar code and automatically show the information on the data base regarding that info of that item
3.4.2. Non-functional
3.4.2.1. performance- should take no longer than a few seconds
4. Group 317
4.1. Knowledge Management Technology
4.1.1. What can it show?
4.1.1.1. Summarize information given to company by employers and workers- analyze patterns, identify potential matches, organize by target segment and industry, maintain relationships with customers who are no longer using the service, retrive information from past matches made.
4.1.2. Functional Requirements
4.1.2.1. Provide City Workforce with the information it needs in order to make decisions and match employers with workers.
4.1.2.2. Share valuable information throughout organization as well as offices across Canada.
4.1.3. Non-Functional Requirements
4.1.3.1. Speed, easily accessable, reliable
5. Group 316-MoveIT
5.1. GPS
5.1.1. Functional Requirements:
5.1.1.1. Must be able to link right customer information with right address
5.1.1.2. Must be able to precisely locate address
5.1.2. What can it show:
5.1.2.1. productivity of workers
5.1.2.2. Location of trucks
5.1.3. What can it do
5.1.3.1. What can it do: locate moving trucks and the progress of the move
5.2. Cell Phone
5.2.1. What can it do: Connects employees with the firm and customers with the business
5.2.2. Functional requirements
5.2.2.1. Must be able to have a secure connection
5.2.3. What can it show:
5.2.3.1. how many customers are contacting us via phone rather than our website
5.3. Cloud Computing (Dr. Mover & Sales Force)
5.3.1. What can it do: connects business with partners and allows them to share data
5.3.2. What can it show: data points, trends
5.3.3. Functional Requirements: Must allow users to search up customer/partner information
5.3.3.1. Must have good security
6. Group 315 - DataMed
6.1. ID Card
6.1.1. Allows patients to access online profile using number on ID card along with user name and password
6.1.1.1. Allows clinic to pull up patient information in their internal system
6.1.2. Brings up all patient information past and current
6.1.2.1. Must be able to bring up all patient information
6.1.3. Doctors are able to update information in system which will be reflection when ID card is used
6.1.4. If patients lose card they will need to have security questions to access patient information and to give them a new card
6.2. Wireless Technology
6.2.1. Need secure system so that database and patient information cannot be hacked into
6.2.2. Be able to pull up the patients profiles using there ID card through the internet
6.2.3. should be portable so that physiotherapists/doctors can move from room to room with ease
6.2.4. Physiotherapists and doctors need there own login to access the system
6.3. Online Patient Profile
6.3.1. profile should be able to be open on portable device (i.e. cell phone, ipad...)
6.3.2. Only patients and their physiotherapist/doctor should be able to access there private profile
6.3.3. Other patients should only see what each individual patient wants them to see (i.e. patients can make quesitons and comments public if they wish to share them or get advise)
6.3.4. Implement security system to make sure patients and their doctors only, have access to the private information posted on profile
6.3.5. Need to update immediately - so as soon as physiotherapist update exercises patients can access this new information
6.3.6. Doctors are able to update certain things that patients aren't allowed to (ex. Physiotherapist is able to update exercises whereas patient can't)
7. Group 314
7.1. SugarCRM
7.1.1. Cloud Computing
7.1.1.1. Integrated database [from local source] uploaded to SugarCRM fulfills real-time editing capabilities for customer information
7.1.1.2. SugarCRM application installed on computers/mobile phone gives versatility on providing information needed from the database
7.1.1.3. SugarCRM plugin applied to all Office softwares for real-time updates provides the capability to generate forms or simple charts to give detailed analysis
7.1.1.4. The need for security is provided by local firewall and SugarCRM/Partner certified secure online database - also access via username/password can be put into tiers limiting the ability to view/edit information
7.1.2. Social CRM
7.1.2.1. SugarCRM social networking integration fulfills company's ability to look through client profiles and address personal issues through messaging, also fulfills the need to make in-profile network announcements/updates through Facebook/Twitter
7.1.2.2. SugarcCRM fulfillfs the need to centralize emails to and from the firm
7.1.2.3. SugarCRM's capibility to integration with different online meeting/chat programs fulfills the need for the firm to be able to communicate with clients whenever needed
7.2. Financial Tools
7.2.1. NOTE: Investor NeuroMaster has been bought out by Track n Trade
7.2.2. A running operating system and database
7.2.2.1. Track n' Trade collects all information from clients' about their background and investments and stores it all on any running database thus creating individual portfolios
7.2.2.2. The program has an external application that can be installed on mobile phones to give information to the clients when needed
7.2.2.3. It has a ability to integrate with any operating system since it is a open source program
8. Group 312
8.1. CEM
8.1.1. Knowing Expectations
8.1.1.1. Flexibility
8.1.1.1.1. High - can record changes in customer customization and personal information
8.1.1.2. Performance
8.1.1.2.1. High – IT solution is very well suited to improve customer customization by improving/organizing communication
8.1.1.3. Scalability
8.1.1.3.1. High - can buy more servers to adapt to volume increase of customers
8.1.1.4. Availability
8.1.1.4.1. High – software; can easily access by turning on computer
8.1.2. - What information we need to implement CEM?
8.1.2.1. o Resources such as customer data and servers
8.1.2.1.1. Customer data is the main source to maintain our competitive advantage which is to personalize our moving service according to customers’ wants. We need to know what they want in order to tailor the service accordingly.
8.1.2.2. o Likes vs. dislikes –> analyze needs, wants
8.1.3. - People
8.1.3.1. o Monitor and develop CEM
8.1.3.2. o Show employees how to direct customers to the website to input info that will eventually be collected through the site for CEM
8.1.4. Functional
8.1.4.1. o Information-oriented
8.1.4.1.1. Customer customization - customer data (personal information (name, address, DOB, contact info, etc…), wants/desires in moving service, requests, changes to data
8.1.4.2. o Process-Oriented
8.1.4.2.1. Needs to be able to sort, input, hold, search, recall custom customization (as stated above)
8.1.4.3. Create automatic back-up for customer data instantly
8.1.4.4. o Has to be able to network and take data from Move IT’s other mediums of media (website, telephone, e-mail, etc…)
8.1.5. - Non-functional
8.1.5.1. Operational
8.1.5.1.1. Has to be able to network and take data from Move IT’s other mediums of media (mail, smartphones, computers, tablets, etc…)
8.1.5.2. o Performance
8.1.5.2.1. Should be able to load individual customer customizations within 5 seconds
8.1.5.3. o Security
8.1.5.3.1. Only authorized personnel should be able to access Move IT`s database and records
8.1.5.4. o Cultural, Political, legal
8.1.5.4.1. Customer data collected for Move IT`s CEM should be secured to ensure personal data isn`t improperly used and comply with privacy laws
9. Group 311
9.1. Web ERP
9.1.1. Acquisition of open source software
9.1.1.1. New node
9.1.2. Implementation of the system across all stores
9.1.2.1. Database needs to be updated frequently and accurately
9.1.3. Suppliers have to be notified and facilitated into this system
9.1.3.1. System should be easy to access and use in order for suppliers to understand and be able to utilize the information that they are provided
9.2. POS System
9.2.1. Points system
9.2.1.1. Should be easy for customers to view the amount of points they have accumulated
9.2.1.2. Customers should be given straight-forward information on how to redeem their points, and the benefits they will reap...
9.2.1.3. CRM system - automatic email alerts to notify how many points customers each have
9.2.2. New node
9.3. Website
9.3.1. Customizable Recipes
9.4. Pick-up service
9.4.1. Information that customers input in the website should be quickly and reliably relayed to the store
10. What are the requirements for implementing the technology you proposed in phase 5 in your company?"
11. New node
12. New node
13. New node
14. New node
15. New node
16. New node
17. New node
18. New node
19. Group 306 - City Workforce
19.1. integrated talent techonlogy
19.1.1. Non functional
19.1.1.1. Performance
19.1.1.1.1. match should take no more than 2 seconds
19.1.1.1.2. should have a large capacity to hold data
19.1.1.2. Security
19.1.1.2.1. Requires a password to access account (customers)
19.1.1.2.2. Only employees in City Workforce can see complete profiles
19.1.1.2.3. Separate log in information
19.1.1.2.4. Firewall/antivirus programs should be in place
19.1.1.3. legal
19.1.1.3.1. data gathering should comply with privacy laws
19.1.2. Functional
19.1.2.1. process oriented functional requirement, need to allow user to match profiles of employers and employees based on available information through various criteria
19.1.2.2. Need be able to search career information and history on our clients to better serve the customer
19.1.3. It is a technology that uses a search engine to match all existing profiles that exist online of a customer (company and worker) to match customers
20. 307 VanRealty
20.1. Cloud Computing
20.1.1. Tangible
20.1.1.1. Money
20.1.1.2. Computers
20.1.1.3. IT personel
20.1.1.4. Training for employees
20.1.1.4.1. Showing the agents that CC hosts economic benefits
20.1.2. Intangible
20.1.2.1. Access to google maps
20.1.2.1.1. Done through salesforce
20.1.3. Functional
20.1.3.1. Hosts the entire company platform under one database
20.1.3.1.1. Objective: Organization, Efficiency, Communication, etc.
20.1.4. Non Functional
20.1.4.1. Realtime
20.1.4.1.1. Data can be accessed quickly and at a realtime rate
20.1.4.2. Lower bandwidth (for smartphones)
20.1.4.2.1. Quickness for browsing
20.1.4.3. Security
20.1.4.3.1. Privacy of information
20.1.4.4. Ease of access
20.1.4.4.1. Efficiency
20.1.4.5. Company organization
20.2. MLS Application
20.2.1. Tangible
20.2.1.1. Money
20.2.1.2. Smartphone
20.2.2. Intangible
20.2.3. Functional
20.2.3.1. Connects potential buyers with their potential purchases
20.2.3.1.1. Objective: $
20.2.4. Non Functional
20.2.4.1. Variety and Efficiency in browsing
20.2.4.2. Quality MLS data
20.2.4.2.1. Usable information --> Client knowledge
20.2.4.3. Deal of the day
20.2.4.3.1. Promotions
20.2.4.4. Use customer information to suggest properties of interest
20.2.4.4.1. Based on information that looks at the clients past browsing (RECOMMENDED FOR YOU)
21. Group 308
21.1. RFID TAGS
21.1.1. REPORTS AND forms The type of produce needs to be recorded in the report, while the forms fill out harvest date, arrival date
21.1.2. Startup Costs/ continuous costs are feasible Tags cost 0.14$ each and the reader is a one time cost of 1,245$
21.1.3. Availability -- many firms have already implemented this technology, will not be hard for produycders ad they will be familiar with this
21.1.4. How to measure performance? If the food is kept fresh, and customers are satisfied (comment cards)
21.1.5. Business Process 1) data warehouse to store all the information regarding the product 2) trained personnel to monitor the information to ensure freshness and timely delivery 3) communicate to the suplliers and ensure they understand out demands
21.1.6. Functional requirements
21.1.6.1. Process-oriented, this process performed by the system will allow users to scan the RFID tags and obtain information about harvest and delivery date
21.1.6.2. Information oriented: the system has accurate information about harvest date and delivery date
21.1.7. NON Functional requirements
21.1.7.1. Operational: This information will be available via the scanners, and computers (Where staff will input them in later)
21.1.7.2. Performance: The dates will show up on the scanner immediately, they can also be accessed later on the computer
21.1.7.3. Security: Cannot be turned off, but without the scanners, the data on the RFID tags cannot be read. Also the information on the RFID tags are not a form of competitive information
21.1.7.4. CULTURAL POLITICAL LEGA:L This data gathering complies with privacy laws
21.1.8. Architecture
21.1.8.1. Data -- will be backed up, disaster recovery will be possible because there will be more than one copy of the file (many computers in the store will have this data Security -- every employee will have a passcode, where they need to input it before they can access the data
21.2. Smart Phone App
21.2.1. Infrastructure Architecture
21.2.1.1. Technical platform: iPhone (ioS) and Android
21.2.1.1.1. Both of these platforms are widely used and popular in the smart phone market. Therefore it is readily available, scalable, and reliable
21.2.1.1.2. Possible issue regarding Apple's apps being a controlled market, ie. they must be approved by Apple before being released. Android is relatively more open, and does not require the same level of approval
21.2.2. Application Architecture
21.2.2.1. Very common ecommerce application, so it should be easily reusable, the software architecture should already be present
21.2.2.2. There will be an issue with getting our databases to connect with two different sources of information such as the android and the iOS, rather than the database only communicating with one OS
21.2.2.3. Expansion of services should be easy as there is a lot of flexibility in both platofrs, but it can be costly as it needs to be updated on both apps, andorid and ios
21.2.3. Data Architecture
21.2.3.1. One database on customer information, one database on current inventory, one database on recently purchased products
21.2.3.2. When a person uses the smart phone app, the app will gather information from the other databases to show the current inventory that is available to purchase. They can view their purchase history, which may speed up their shopping process. Lastly, we will keep their customer information on hand for when they purchase
21.2.4. Functional Requirements
21.2.4.1. Process Oriented: Our app must allow customers to browse and purchase groceries through the app
21.2.5. Non-Functional Requirements
21.2.5.1. Operational
21.2.5.1.1. The app should be viewable on iPhones and Android devices.
21.2.5.2. Performance
21.2.5.2.1. The app should load quickly, without dead links, images, etc.
21.2.5.2.2. The app should be able to handle a large capacity, so that it does not crash if there are a lot of users accessing the app at one time
21.2.5.3. Security
21.2.5.3.1. It has to be using a secure encryption method, as it may be possible that credit card information is being sent over wirelessly so we can charge them
21.2.5.3.2. If we run user specific promotions, and if we do implement it into the application, then we need to make sure the appropriate access rules are granted for the specific prootion
21.2.5.3.3. We have to make sure that people are only seeing what they are supposed to see, so we have to ensure that in the recently purchased items, it is what they have recently purchased, rather than things which they hvaent purchased, which could also create some sort of legal information, as it could be someone else's data we are spreading around to our users
21.2.5.4. Cultural Polital Legal
21.2.5.4.1. The system will be gathering a lot of data on the user, particularly information which could be sensitive, so all the data which we recieve must be secured to save us from the legal issues
22. Group 302- Good Foods Canada
22.1. Website (which utilizes CRM: operational and analytical)
22.1.1. Money to install the CRM oftware
22.1.1.1. New node
22.1.2. Employees to manage the system
22.1.2.1. include training
22.1.3. In order to implement an effective CRM system the requirements for the following steps should be consider: 1.collection of information 2. Storing information 3. Accessing information 4. Analysing customer behaviour 5.Marketing more effectively 6. Enhancing the customer experience
22.1.3.1. step one requirment: surveys and questionnaires. sign up forms for the online store. Data about past consumers behaviour . step two: storing information- data base is required. step three: accessing information: set up analytical CRM, requirments: buying the software. step 4: analysing consumer behaviour.
22.1.4. Functional Requirements
22.1.4.1. Informative requirements
22.1.4.1.1. The system must be able to record who our buyers are, who our most notable consumers are and what they buy
22.1.5. Non-functional requirements
22.1.5.1. Security: Protect the privacy information of consumers such as their billing information
22.1.5.2. Be able to store the past information of purchasing behavior to implement the Personalization system
22.1.5.3. Must be able to link pages properly (sequential--> choose your products, add to the cart, billing information)
23. Group 305- VanRealty
23.1. 0
23.2. data architecture
23.2.1. functional
23.2.1.1. backup and recovery system
23.2.2. functional
23.2.2.1. make sure that clients information is kept private
23.2.3. New node
23.3. infrastructure architecture
23.3.1. flexibility
23.3.1.1. functional
23.3.1.1.1. everyone can use it because its online
23.3.2. reliability
23.3.2.1. functional
23.3.2.1.1. easy to update
23.3.3. availability
23.3.3.1. functional
23.3.3.1.1. can use 24hrs
23.3.4. performance
23.3.4.1. functional
23.3.4.1.1. needs to be quick and efficient
23.3.5. scalability
23.3.5.1. non functional
23.3.5.1.1. need a developer to monitor the website and update
24. Group 304
24.1. App
24.1.1. Internal Application
24.1.1.1. Functional
24.1.1.1.1. Managing
24.1.1.1.2. Monitoring Clients
24.1.1.1.3. Data input
24.1.1.1.4. Sending information to clients\
24.1.1.2. Non Functional
24.1.1.2.1. Security
24.1.2. External Application
24.1.2.1. Functional
24.1.2.1.1. News feed
24.1.2.1.2. Financial Tools
24.1.2.1.3. Communication w/ advisors
24.1.2.1.4. Investment Information
24.1.2.1.5. Performance of investments
24.1.2.2. Non Functional
24.1.2.2.1. Security
24.1.2.2.2. cross platform
25. Group 303: VanRealty
26. Group 309 - MoveIT
26.1. DATS - Will need:
26.1.1. Functional
26.1.1.1. Informational
26.1.1.1.1. must show employee certifications
26.1.1.1.2. must show employee jobs
26.1.1.2. Process
26.1.1.2.1. head office/ location to store computers
26.1.1.2.2. employee access to computers
26.1.1.2.3. people to implement
26.1.2. Non-Functional
26.1.2.1. should comply with privacy laws/company policy
26.1.2.2. only managers should be able to see all employee files, even though all employees will have limited access
26.1.2.3. will likely need windows and pc
26.2. GPS
26.2.1. Functional
26.2.1.1. must have traffic receiver
26.2.1.2. must be satellite based
26.2.1.3. must be cost effective
26.2.2. Non Functional
26.2.2.1. should help with weather conditions
26.2.2.2. should have an easy to use interface
26.2.2.3. should calculate routes quickly
26.2.2.4. should calculate the most efficient routes based on traffic,fuel efficiency and time
27. Group 310 - City Workforce
27.1. Recommendation Agent
27.1.1. Functional Requirements
27.1.1.1. Access all database information
27.1.1.2. Sort through database to find optimal matches between employers and employees
27.1.1.3. Able to be accessed by certain employees and managers to over-ride and create changes in its structure
27.2. Payroll Technology
27.2.1. Functional Requirements
27.2.1.1. Automatically pay employees for clocked hours
27.2.1.2. Provide a system for employees and employers to submit and track worked hours
27.2.1.3. Automatically charge employers monthly fee's based on work package
27.3. Cloud Computing
27.3.1. Functional Requirements
27.3.1.1. Provide uploading capabilities of all profile information for companies and employees into the database
27.3.1.2. Be accessible from multiple locations and by multiple people at the same time
27.3.2. Non-functional Requirements
27.3.2.1. Mobile access for managers and decision makers
27.4. Knowledge Management Software and Infrastructure
27.4.1. Functional Requirements
27.4.1.1. Allow certain employees to access database
27.4.1.2. Store information regarding jobs, employees, and employers
27.4.1.2.1. Continually add new user data through our website to our database
27.4.1.3. Be organized and have a user-friendly interface to perform queries, etc.
27.5. Security MGMT and Confiirmation System
27.5.1. Functional Requirements
27.5.1.1. Make sure only certain employees of our organization have access to certain information
27.6. Mobile Application
27.6.1. Functional Requirements
27.6.1.1. Allow a user to update profile information
27.6.1.2. Allow a user to look for new work opportunites
27.6.2. Non-Functional Requirements
27.6.2.1. Accessible on multiple devices and formats
28. Group 301 ver.2
28.1. GPS
28.1.1. Functional
28.1.1.1. Navigation system - Direct drivers to the designated place
28.1.1.2. Tracking - Moving process + supervision of employees
28.1.1.3. Capability - The system needs to be compatible with the company database
28.1.2. Non-Functional
28.1.2.1. Connection between drivers and management needs to be consistent to ensure security
28.1.2.2. Accuracy (updated)
28.2. ERP
28.2.1. Functional
28.2.1.1. Customer data and employee data need to be recorded
28.2.1.2. Help match employee skills with the right customer
28.2.1.3. Make service quotes and estimates on moving costs
28.2.2. Non-Functional
28.2.2.1. Integration of different IS, all pieces of data are synchronized, so management and employees can update profiles more efficiently
28.2.2.1.1. Reduces unnecessary communication
28.3. Knowledge Management System
28.3.1. Functional
28.3.1.1. Reliability of records, need to make sure the info provided is valuable for us to make use of
28.3.1.2. Must obtain reference of past success and failure
28.3.1.3. Must obtain records of completed projets
28.3.2. Non-Functional
28.3.2.1. Scalability of past success and failure, so management can decide on which areas to focus on or to improve