COMM391 Section 203 Phase 7

COMM391 Section 203 Phase 7

1. Cultural, political legal

1.1. Multilingual support, multiencoding support

1.2. Multilingual support, multiencoding support

1.3. The web app should be prepared for different laws regarding transactional activities.

2. Information System to be implemented by CW: Recommender System & Intelligent Agents using an ERP to implement internal an external information into one system. Non-functional requirements: Operational: Employees/ers should be able to fill out online forms. Submission of information has to be accessible for clients. A good website is important. The matching results should only be accessible internally incorporating the factors the system used to weigh the matches. Operators will evaluate this match and then provide suggestions for clients. Performance: The system does not need to be fast, however it has to be extremely reliable and error free. Therefore a constant error log is important. Expansion of capacity has to be easy. Security: Important since a lot of personal information is stored in the databases. Therefore both employees and employers need to sign a release of information form. Infromation from employees may only be accessible to employers upon verfication through CW's operators. Also, the information visible to employers needs to be anonymised - no name, age, picture etc. - until the employee is contacted. Cultural, Political & Legal: Privacy laws apply and the system has to comply with them. Also, labour laws and bargaining laws have to be respected. Minorities have to receive equal treatment. Functional requirements Process oriented: Easy search to find suitable matches between employer & employees. The ERP will enable the composition of external and internal information to make it easily accessible and provide a good match. Information oriented: Comprehensive information on employers needs and employees skills- this information is provided internally through performance and feedback reviews; and through external sources such as the job profile created by the employer and the employee profile created by the job seeker. The latter information need is essential for the system to create internal information.

3. For Datamed Medical, the technology is Enterprise Resource Planning which connects information system together, and share data between doctors and clients. Functional requirements would be the actual data we collect and keep track of the patients. The non-functional requirements would include: performance, reliability, security, political and legal aspects of the system. For performance aspect, we want to make sure that the website can be easily navigated, the website can be quickly loaded within 2 seconds, and both doctors and clients can constantly update data without difficulties. In terms of security, we want to make sure that no third party can access the data without permission and it can not be easily hacked. On top of that, in terms of the legal aspect our non-functional requirements, our data will also adhere to the BC Privacy Law. Operational aspect: mobile, website, anywhere that's internet-accessible. Together with the functional and non-functional requirements we mentioned above, this will ensure us a smooth and successful ERP system that will allow us to communicate effectively while protecting sensitive patient data.

4. - it must allow customer feedback to be inputted on various devices (Mac's, Windows, smart phones etc...) - the system automatically sorts the information and finds the services that best match the clients needs - its must allow the employee to then input the information found into our database - its must save and update the database based on the new inputs - we can then use this information to rank the services

5. VanRealty - Cloud Computing

5.1. Non-functional Requirements

5.1.1. Operational

5.1.1.1. The system must be able to run on a smartphone, tablet, computer, etc. It must also be able to run away from the office, while showing houses to clients.

5.1.1.2. Agents must be able to use the system to edit data and integrate the changes into the system, while doing house showings.

5.1.2. Performance

5.1.2.1. The system must be able to retrieve the data that agents are searching for fast, in order to provide answers or comments to clients about their concerns or questions. (Ex. if a client asks to see more houses than suggested listings, the agent must be able to retrieve data about available listings quickly and on the spot)

5.1.3. Security

5.1.3.1. The system must have various access levels and/or passwords, so certain data is only viewable and may only be edited by agents. All other users(clients) will only be able to view certain data and not edit it.

5.1.4. Legal

5.1.4.1. The data available to clients through the system, must comply with Canadian privacy laws. (Ex. clients should not be able to access any data related to other clients, like contact information)

6. Process-Oriented

6.1. The system must allow users to create a custom profile complete with login username.

6.2. The system must allow users to interact in a message board community and access educational information provided by the website.

6.3. The system must allow users to reserve organic food products in store. The system must keep in-store inventory in real time so users are reserving available products.

6.4. The system must be able to map the fastest route to the nearest Good Foods Canada products carrier that holds the reserved products of the users. This system must be able to locate users (either based on IP address or GPS systems from smart phones) and locate stores with available products. The mapping aspect of the system must be integrated with a popular map technology such as Google Maps for user convenience.

7. Group 318- DataMed: Cross Enterprise Document Sharing System

7.1. Functional Requirements

7.1.1. During appointments, our doctors can pull up files and apply live updates, allowing the charts to be more interactive and complete. Furthermore, documents can be shared between any healthcare enterprise, which facilitates the potential transfer of healthcare records. By implementing a text mining system onto this XDS we will look for critical points, be able to analyze a patient’s history, and immediately pull out eligible potential candidates. This enables our company to aid the public system, as when these patients are scheduled onto the waitlist for a surgery, they are given the option for faster service at our clinic. We are then able to minimize wait time for all patients – no matter where they are looking to receive help.

7.1.2. It is document content neutral so that any type of document encoded in compliance with a widely accepted standard can be shared. Therefore, this document centric architecture offers mechanisms to publish query and retrieve specific clinical documents for a specific patient.

7.1.3. Security must be ensured, as all of our patients' private documents will be recorded on our database.

7.2. Non-Functional Requirements

7.2.1. Basic Requirements

7.2.1.1. Must be highly responsive in that our system must have quick response times. Especially as our doctors will be applying live updates, we need to be able to quickly register new information so that our doctors can maximize time spent with patients.

7.2.1.2. Multiple people need to be able to access our system at the same time. Since different clinics are sharing information yet have the same working hours, we need to ensure that our system is advanced enough so that we can support heavy traffic.

7.2.2. Additional Requirements

7.2.2.1. Multiple people need to be able to access our system at the same time. Since different clinics are sharing information yet have the same working hours, we need to ensure that our system is advanced enough so that we can support heavy traffic.

7.2.2.2. Compatibility with future Canadian Infoway system. We are hoping to expand our system to be able to further work with the Canadian public system, since our value proposition leads that we align the public and private sectors. This is a large reason for why we chose the XDS system. Also, the system is easy to adopt, like public transit, so when and if other clinics decide to work with us, they can "hop on" as easily as getting onto a bus.

8. Additional Requirements

9. Electronic Health Record

9.1. Non-Functional

9.1.1. Print formats, convenient and faster access to patient information. Information can be backed up

9.1.2. Backupable, Back up the information in case the data get lost.

9.2. Functional

9.2.1. Information management - gathering all the information from the patients and effectively managing information load

10. Performance

10.1. Succesfuly increase profits under all circumstances, i.e. in both volatile and non-volatile markets, and in bear and bull markets

11. Operational

11.1. Have a resonable cost as we are a small investment firm

12. Operational: The feedback form should be accessible on tablets and it should be easy to edit and submit directly to the database

13. The system has to have information on customer feedback: This is essential in implementing our personalized marketing system. If this information is not available then there will essentially be no basis for the personalized marketing system

14. New node

15. Non-functional

16. Group 301

16.1. City Workforce - Recommendation Agents

16.1.1. Functional

16.1.1.1. Process-oriented

16.1.1.1.1. Must generate possible matches to agents, helping agents set up basic matching requirements. The system has to be able to search through profiles and provide a list of appropriate and suitable candidates to clients so agents can personally finalize matches. This is ultimately the main purpose for the agency to implement the system. (Do primary work for agents to lessen work load and make the process more efficient.)

16.1.1.2. Information-oriented

16.1.1.2.1. Must have profiles of candidates and clients. The system must have detail information on both candidates and clients including preferences, past experiences, skill requirements, company cultures and personal characteristics. The system should also store all information gathered from interviews with candidates and clients. This information provides the basis for the system's process. Without the information, the system will not be able to make accurate primary matches between candidates and clients. So, the system must be able to maintain precise records of customers to make the most updated and accurate matches between candidates and clients.

16.1.2. Non-functional

16.1.2.1. Operational

16.1.2.1.1. Selected information from the system should be viewable to the candidates and clients on our websites through their personal accounts. Agents should be able to directly enter the system to view primary matches and handle customer accounts. Only specific information released by agents to candidates and clients should be available to candidates and clients to protect the privacy of customers.

16.1.2.2. Performance

16.1.2.2.1. Information should be generated quickly for agents and customers. (Within a day of when the data is entered into the system) Information should also be as accurate and reliable as possible. The system should frequently update to meet new demands and preferences of candidates and clients as new information is gathered. The system should also be able to handle large amounts of data as it will need to store all the information available about customers so that it can provide the primary matches between candidates and clients. It should also be able to handle large amounts of traffic at the same time so that many agents can be using the system at the same time. The website hosting information for candidates and clients should be also be able to handle high volumes of traffic in order to provide convenience for customers to use the system at any time they require.

16.1.2.3. Security

16.1.2.3.1. The system should keep all information completely private to the agency. Candidates and clients will only have limited access to these information through the agents at our company. This will allow customers to access information about their personal accounts, but also give enough protection to all other customers' information. This information is valuable not only to our company, but also to candidates and clients, thus cannot be leaked to anyone in the market.

16.1.2.4. Cultural, Political, Legal

16.1.2.4.1. The system's data gathering should comply with privacy laws, human rights laws, employee rights laws and employment standards acts. This can ensure customers that the company gathers and handles data in a proper and fitting manner, giving them the confidence in the company's matching procedures.

17. QuestWhat are the functional and non-functional requirements of the information system you want to implement in the organization?ion

18. Group 305

18.1. DSS: Quoting system

18.1.1. Functional

18.1.1.1. Process

18.1.1.1.1. Employees need to be able to both input past data and extract information in the form of a quote

18.1.1.1.2. Must be able to search through past job data

18.1.1.1.3. Must be able to operate with different data inputs: e.g. number of bedrooms instead of square footage

18.1.1.1.4. Should be able to take data from the customer (ie. square footage, number of bedrooms, address moving from and address moving to [to give distance moved]) to then correlate to cost information from past moves for each of the categories that a customer will be charged for (ie. number of movers and trucks, time spent moving, number of boxes) which will provide a quote to be relayed to the customer

18.1.1.2. Information Orientated

18.1.1.2.1. it must have information on all past moves yet adjust to use the information that is most relevant to the specifics of the next job, such as based on th eneighbourhood (cannot just pick random ones)

18.1.1.2.2. The system must be able to continually adjust to new information in order to create accurate quotes.

18.1.2. Non-funcation

18.1.2.1. Operational

18.1.2.1.1. Readability: easy user interface (easy for employees to interpret and understand information being provided by the system), it should therefore provide the specific final amount and break down the quote into the different costs which MoveIT will charge for (ie. this can allow the quote to be adapted to whether the customer wants a packing service or not)

18.1.2.1.2. Ability to work on more than one computer within the office (to allow more than one sales representative to use it at once).

18.1.2.1.3. Can be accessed away from the office (cloud computer may be helpful)

18.1.2.2. Performance

18.1.2.2.1. A relatively large capacity which will store information about all our current and past customers from 3-5 years of jobs: this will ensure that the information can be adjusted to a variety of circumstances (ie. different neighbourhoods) by not having to delete older data due to space issues

18.1.2.2.2. Ability to give a quote within a few seconds: because quotes will be given while customers are on the phone with a sales rep. For online version it can take up to 30s

18.1.2.3. Security

18.1.2.3.1. Customer information should be secured from 3rd party access

18.1.2.4. Cultural, Political, and Legal

18.1.2.4.1. Customers privacy should be respected and information cannot be released to outside individuals, and only to those with clearance within the company (ie. movers should not have easy access to costing information from old moves)

19. Group 306

19.1. Functional requirements: -Job-order profiles: need the system to produce reports for daily schedules, -Training manual/ incident database: system must be able to summarize the most occurring high/low rated employee behaviours into a report. -Equipment profiles: Need to track employee use of equipment on trucks for availability/maintenance -Storage space tracking: Need to produce report of how current warehouse space has been allocated to customers and what is available -Historical route data: user must be able to type in a street and be given the most recent input data about that route. -Trend analysis for hiring: must be able to produce an easy to read graphical representation of historical overtime/idle time.

19.2. Non-functional requirements: -low cost - usability is a large requirement: system must be simple to use as the employees have no experience with technology in the office. (this will help decrease cost of the implementation by decreasing training time). To defign "simple to use" in this context, we mean that it takes very few steps (2 or 3) to complete a task such as inputting a new job/employee/ etc. -must be able to back-up data, collection of data is for long-term goals, therefore a system crash and loss of information would be devastating. -follow Canadian security laws and CCMTA regulations. -extensibility and compatibility- be able to add to/transfer information from system.

20. Group 307

20.1. VAnalyst

20.1.1. Functional

20.1.1.1. Process-Oriented •The system must allow employees to browse through and retrieve the information of all previous clients and customers. •The system must also allow employees to add and save new information gathered on customers •The system must allow employees to add new customers to the database •The system must be organized in different groups depending on which employee they worked through or based on their level of wealth. Information-Oriented •The system must contain information about all previous and current customers •The system must include the customers: - name, age, family status, and occupation - income and salary levels - transaction history with VAnalyst - short-term and long-term goals

20.1.2. Non-Functional

20.1.2.1. Operational •The information should be accessible from employees’ home computers or smartphones •The system must be accessible from any computer in VAnalyst’s office •The third-party organization’s server where the data is held shouldn’t be prone to system crashes or failures. •The system should be designed to include the ability to handle multiple currencies and languages •VAnalyst should withhold the “five 9s” standard of available for their software as a service, CRM software system •Employees should be well-trained and familiar with the software as a service system, CRM software before using it. Performance •Information on the software system should be accessible when one wants to access it. •Information should be organized effectively and logically so employees can work efficiently Security •All information should be kept privately and only accessible by authorized employees •Passwords should contain 8 or 9 digits, including numbers and capital letters, and should be changed and updated frequently Cultural, Political, and Legal •The information gathered on clients should comply with privacy laws

21. Group 316

22. Group 317

22.1. MoveIT- DSS: Scheduling system

22.1.1. Functional Requirments

22.1.1.1. Need to be able to collect customer information (Truck needed, time slot, location etc) to allow for proper scheduling.

22.1.1.2. customers must be able to access the system online to input their data (through website)

22.1.1.3. Use availability information on workers, trucks to create an availability schedule online for customers to view

22.1.1.4. Must be able to send information when a customers books a move to management in order to process the order. Then update the schedule to no longer include this time slot as avaialble

22.1.2. Non-Functional Requirments

22.1.2.1. Cheap to build, implement. Easy to intergrate with the website and our systems

22.1.2.1.1. cost savings/revenue improvements provide a large enough ROI to MoveIT making it worthwhile

22.1.2.2. Gives an easy to read report on the scheduling information ( what driver, what truck, what time etc)

22.1.2.2.1. Allows customers to easily view the time slots available to move

22.1.2.3. Should have barriers to prevent external users from hacking the system and creating changes and/or stealing clients infotmation

22.1.2.3.1. Have back up files of information just incase the system is hacked or the system crashes.

22.1.2.4. System constantly renews itself very quickly less than 2 seconds for the most updated information and has a large enough capacity to store all new information + past records

22.1.2.4.1. information must be available in a timely manner for management to use the information and make changes

22.1.2.5. The data gathered will abide to the government's privacy laws (customers are informed about the use of their data)

22.1.2.6. management must be able to search for specific job details to find information on historical jobs (i.e search for customer names, trucks used, etc)

23. Group 318

24. Group 319

24.1. Functional

24.1.1. The system has to have information on past customer moves: Because we plan on using past data to predict future moving trends as well as provide more accurate estimates. Then the system has to have as detailed information as possible on customer moves.

24.1.2. Information Oriented

24.1.2.1. The system has to have information on customer feedback: This is essential in implementing our personalized marketing system. If this information is not available then there will essentially be no basis for the personalized marketing system

24.1.3. One database will be created to include all information collected about customers from the website, emails, phone, and employee interaction during the moving process. This will be the most basic requirement of the information system needed.

24.1.4. New node

24.2. non functional

24.2.1. Security The system should be accessible by authorized users only as it will contain personal information on customers such as th eir address and contact information and perhaps credit card information

24.2.2. Operational: The feedback form should be accessible on tablets and it should be easy to edit and submit directly to the database

24.2.3. Legal Not only should the Information system comply with privacy laws but also regulations set by the federal motor carrier safety administration (FMCSA) which regulates moving companies

24.2.4. After user/customer inputs their data, the database/IS will present a quote on the website email, including reviews from past users.

24.2.5. The Information System must be user friendly and easy to understand, since the employees might not be tech-savvy people. Comprehensive system will decrease the learning curve and shorten time required to use. Our system will be intuitive so that information can be extracted and inputted without difficulty.

25. Group 320

25.1. TPS - eCommerce Website

25.1.1. Functional

25.1.1.1. Process - Oriented

25.1.1.1.1. Users must be able to search through listings based on certain criteria; square footage, location, price etc.

25.1.1.1.2. Agents must be able to see past transactions to identify customers with buying patterns.

25.1.1.1.3. The system must be able to make recommendations based on past listings viewed and criteria selected by buyers.

25.1.1.1.4. The system must be able to make recommendations based on past listings viewed and criteria selected by buyers.

25.1.1.2. Information - Oriented

25.1.1.2.1. The system must have information on all of VanRealty's agents, buyers/sellers

25.1.1.2.2. The system must have information

25.1.2. Non-functional

25.1.2.1. Operational

25.1.2.1.1. Web application must be accessible by smartphones and viewable on all Internet browsers.

25.1.2.2. Security

25.1.2.2.1. Only VanRealty agents should be able to view past transactional activities.

25.1.2.2.2. Sellers should be able to hide the address of their homes.

25.1.2.2.3. Web app should be certified by a trusted third party internet security organization.Transactions should be hosted by a legitimate clearing site.

25.1.2.3. Performance

25.1.2.3.1. Each page should take no longer than 2 seconds to load

25.1.2.3.2. Listings should be instantaneous.

25.1.2.3.3. Bandwidth should be sufficient; more than 1000 people should be able to access application simultaneously.

26. Group 315

26.1. VanRealty - Cloud Computing

26.1.1. Non-Functional Requirements

26.1.1.1. Operational

26.1.1.1.1. The system must be able to run on a smartphone, tablet, computer, etc. while agents are away from the office and showing houses.

26.1.1.1.2. The system must provide the data that Real estate agents need while away from the central database (e.g. on house showings). The system must also allow agents to edit/add new data into the system and it must be integrated (e.g. submit a house offer)

26.1.1.2. Performance

26.1.1.2.1. The system must be able to provide the agent with the data they search for quickly and on the spot (Ex. if a client wishes to see more houses than the ones the agent suggested, the agent should be able to quickly search and retrieve that data quickly in order to make the most of clients' time and create the most customer satisfaction)

26.1.1.3. Security

26.1.1.3.1. The system must have various access levels/passwords, so only agents may have access to specific data (e.g.client information) and edit/add data into the system. Clients and potential clients will not have authority to access certain data (e.g. client info) and they have no ability to add/edit data in the database

26.1.1.4. Legal

26.1.1.4.1. The system must comply with Canadian/ BC privacy laws. Ex. clients should not be able to see certain information related to other clients, such as the contact information.

26.2. Functional Requirements

26.2.1. Process-Oriented

26.2.1.1. Real Estate agents must be able to search for any data they may need while showing a house (e.g. additional house listings, offers, etc.)

26.2.1.2. The database must be accessible over a wireless network, when agents are away from the office.

26.2.1.3. Clients must be able to search for data they may need about houses.

26.2.2. Information-Oriented

26.2.2.1. The system must contain data relating to any information that agents might need while out of the office showing houses. This includes but is not limited to asking prices, house details (number of bedrooms, bathrooms, etc.), house listings, client details (name, contact info, etc.), and real estate offers.

27. Group 314

27.1.1.1.1. The system must be able to track popular message board topics, key phrases/words and reservation history of users so Good Foods can customize their offers to users and send personalized educational information

27.1.1.1.2. The system must be able to provide users with the nutritional content of their reservations to track dietary trends of individual users

27.1.2. Non-Functional

27.1.2.1. Operational

27.1.2.1.1. The website should be viewable on smartphones so users can have a mobile shopping experience

27.1.2.2. Performance

27.1.2.2.1. Website loading time needs to be fast

27.1.2.2.2. In-store product availability must be up-to-date so users can trust our system (RELIABILITY)

27.1.2.2.3. The location of the nearest store with available products must be reasonably close to users

27.1.2.2.4. Educational information that we provide to users must be relevant based on the information we have mined from their personal profiles

27.1.2.3. Security

27.1.2.3.1. User information (from website) such as personal information, location (from routing requirement of system) must be kept secure and only be used by Good Foods management

27.1.2.4. Cultural, Political and Legal

27.1.2.4.1. Text Data Mining technology must comply with privacy laws

28. Group 313

29. Group 312

29.1. 312 Good Foods -- Functional

29.1.1. Process-oriented: (1) Our CRM system must also compile our information in a logical manner in order for our managers to easily sort through the data and make decisions based on analyzed data; (2) All customer profile data stored on our CRM system should be directly connected to our in-store kiosks as well as to our online community, which will allow us to integrate all information collected from customer to form a single, interconnected experience

29.1.2. Information-Oriented: (1) Our loyalty card / CRM system must store and manage information on our customer's buying habits, demographics, complaints in order to personalize and improve their shopping experience; (2) Our POS systems must also keep track of when our employees sign in and sign out.

29.2. Non-Functional

29.2.1. Security: Only middle-level managers and higher that are in charge of decision making should be able to view sensitive information

29.2.2. Operational: We are making our website viewable both on standard browsers as well as mobile devices with compliance to web standards for maximum compatibility

29.2.3. Performance: (1) Website and kiosk layout should be logical, user-friendly for best customer experience; (2) the network will have a large bandwidth to accommodate many users at once; (3) system should catch duplicate entries in inventory

31. Group 308

31.1. Functional

31.1.2. It must store data from suppliers, such as best-before-date, supplier ID, Quantity

31.1.3. The RIFD technology has to be included in every step of the supply chain (connect between warehouse, stockroom, retail).

31.1.4. ERP must be compatible with our current POS System, and the data must be able to be easily integrated with pervious inventory data

31.1.5. The new RIFD bins must fit into store shelfs, truck and the warehouse with ease

31.1.6. The ERP must be able to use the data to provide shelf stock information that is accessible to all parities that need to access it

31.1.7. New node

31.2. non-Functional

31.2.1. It has to record the inventory level in a timely manner and the interface should be easy to understand and interact with (user-friendly).

31.2.2. It should also be compatible with future possible technology to facilitate growth. Meaning the RIFD Scanners should be able to read future tags, and also allow us to extend the use of the RIFD technology to a POS system that also incorporates RIFD technology.

31.2.3. It must be faster than the current system of restocking and inventory management

31.2.4. Must be very intuitive and new employees can be easily trained on using the new system, as well as old employees who now need to adopt the system

32. Group 309

32.1. VanRealty

32.1.1. Functional

32.1.1.1. Database

32.1.1.1.1. - it must allow customer feedback to be inputted - it must allow our employees to perform searches in the database to find the services that best match the customer - its must allow the employee to then input the information found into our database - its must save and update the database based on the new inputs - we can then use this information to rank the services

32.1.2. Non-Functional

32.1.2.1. database

32.1.2.1.1. - The transferring of forms/information is quick and easy - The surveys can be filled out online or on paper - The information is secure and can only be viewed by the designated employee - The database will automatically ranks the services based on the input data - Accessible by smart phones and other handheld devices

33. Group 310

33.1. High frequency trading system (HFT)

33.1.1. Functional (MUST)

33.1.1.1. Process oriented

33.1.1.1.1. To increase the efficiency of profitability in volatile markets, and hence better satisfy the strategic role of maximizing portfolio performance in an attempt to retain customers and beat the market average.

33.1.1.2. Information oriented

33.1.1.2.1. The ability to gather and correctly interpret large amounts of data, such as the volumes traded of each stock, the moving averages, determining various support and resistance levels and interpreting this information suitably to be able to earn abnormal profits

33.1.2. Non-functional (SHOULD)

33.1.2.1. a

33.1.2.1.1. Operational

33.1.2.1.2. Performance

33.1.2.1.3. Security

33.1.2.1.4. Cultural/Political/Legal

34. Group 304

34.1. Technology: E-Procurement

34.2. Functional

34.2.1. This system must create, place, and approve order requisitions (between clients and employees) and collect data from employee/client feedbacks.

34.2.2. The system must identify clients for a specific category of hiring requirements.

34.2.3. Must gather and distribute information both from and to internal and external parties using Internet technology.

34.3. Non-functional

34.3.1. The employee profiles should be viewable on smartphones for increased efficiency

34.3.2. Should provide a storage for past records and transaction history.

34.3.2.1. Considered non-functional because it's not required for the business and hiring process, althought it's important to have a database of previous information for reference

34.3.3. Should be simple and user-friendly in order for efficient use between employees and clients

34.3.4. Should be in multiple languages to support our diverse team of employees and clients

35. Group 303

35.1. Mobile E-commerce

35.1.1. Functional

35.1.1.1. Information-oriented

35.1.1.1.1. The system must obtain the information about nutritional facts, prices reflect to diet plan and prices for the food, categorizing diet plan

35.1.1.2. Process- oriented

35.1.1.2.1. Prices on application should be updated according to the price changes from our central system

35.1.1.2.2. The system must allow customers to search through different categories of diet plans as well as different preferences.

35.1.1.2.3. System allows customer to search through different categories, and allows customer to filtrate out on what they allergic to or what are their preferences.

35.1.2.1.4. IT-specialist must be hired to implement and direct all e-commerce decisions and fulfill all the requirements. (ie. Updating/reviewing the data and information used in the app/website; Maintaining/updating the website and apps; etc.)

35.1.2.2. Security

35.1.2.2.1. Must ensure all customers information are private. In addition customer must sign an agreement when applying to become a member (thus having the ability to access to the diet plan)

35.1.2.3. Cost effective

35.1.2.3.1. relatively low cost so we would be able to afford to implement the system

36. Group 302

36.1. Website (With E-Commerce and GPS service)

36.1.1. Functional

36.1.1.1. Process oriented

36.1.1.1.1. Website should re direct customer to questionnaire

36.1.1.1.2. Able to allow users to apply filters and search key words, click on optios to redirect pages

36.1.1.1.3. Domain name

36.1.1.1.4. Should be able to keep track of browsing trends and search statistics

36.1.1.1.5. Provide GPS map service on the website that consists of the listings from the users preferences chosen or filtered from their preferences

36.1.1.1.6. Must have a large capacity so many clients can use tis system at the same time

36.1.1.1.7. Able to predict/recommend listings from browsing trends of users

36.1.1.1.8. Past hisory should be viewable as to identify buying patterns of clientst

36.1.1.1.9. To be able to use our gps system, users should be given a password by the firm to access this service

36.1.1.1.10. Able to matchquestionnaire information with current listing informationt

36.1.1.1.11. Must differentiate beteen confidential information and keep it safe

36.1.1.2.1. Must have all our listings from our servers that number of bedrooms, rooms and etc. location, square footage, price, house age/history

36.1.1.2.2. Data on our current findings on trends

36.1.1.2.3. Linked data for matched searches and GPS locations

36.1.1.2.4. Data on immigration information from CMHMC and MLS sources

36.1.1.2.5. Must have the most updated/recent data on listings to make our match process faster

36.1.1.2.6. New node

36.1.2. Non functional

36.1.2.1. Performance - System must be fast, convenient, and easy to use by both our agents and clients. Should take no longer than 2 seconds to load up maps, retrieve listings, or process the questionnaires

36.1.2.2. Performance - Questionaire should oad quickly, options should be easy to use l

36.1.2.3. Operational - System should be compatible with mobile devices and laptop

36.1.2.4. Operational - Shold be translated for our immigrant target market and easily translatable. Should be easy to assess a.translating program

36.1.2.5. Security - should be able to secure any user information and differentiate between confidential data so that our users will feel safe using the system