Reference no: EM132331628

Case Study -

INTRODUCTION
Eat Organic Food produces organically certified foods. It initially started by using Ian's backyard. It was a large backyard...that had also made use of neighbours' unused land.

ACTIVITY 5
1. What fact-finding techniques, apart from interviews, do you recommend to find out the requirements for the new system?
2. Include the recommendations for other fact-finding techniques, in your Report. Provide enough justification for using those techniques.
3. Identify at least two staff members with different primary job roles of interest to this project for interview.
4. Prepare a list of questions for an interview with each staff member. Identify the time anticipated for the interview. Review your topic on creating interview questions, and make sure you include suitable question types.
5. Include the interview plans (before, during, and after) in the Appendices for your Report.

ACTIVITY 6
1. Write down a list of the main functions needed to be handled by the new system.
2. What are the roles that will be interacting with the system?
3. Write down a list of additional features which in principle could be included in the new system, but are more likely to be held back for now and considered in the future if and when the resulting information system is subject to later review and enhancement(s). Include the list with appropriate descriptions in your report.
4. Using all the information that you know about the EOF business so far, create a use- case diagram (with all actors/users and use cases) for the new system and include it in your report. You may provide enough explanation about the use case diagram.
5. Select four use-cases and write a brief use-case description for them.
6. Pick one of these use-cases and write a full use-case description for it. Draw and use an activity diagram in the full description.
7. You need to have the following in your report:
• use case list and descriptions
• the use-case diagram and its explanation
• brief use-case descriptions for 4 use-cases
• a full use-case description
• an activity diagram

CASE STUDY PART 7
You have been preparing the System Requirement report for Ruth and Ian. From your investigation so far you are leaning towards a recommendation for either in-house development or outsourcing options for the new system. You does not feel that a commercial software package would meet the needs of EOF.
Based on your research you feel that it would be premature to select a development strategy at this time. Instead, you recommended to Ruth that an in-house team should develop a design prototype, using a relational database as a model. You argue that the prototype would have two main objectives:
• it would represent a user-approved model of the new system, and
• it would identify all system entities and the relationships between them.
You explained that it would be better to design the basic system first, and then address other issues, including Web enhancements and implementation options. You proposed a

three-step plan composed of a) data design, b) user interface design, and c: application architecture.
You explained that systems analysts refer to this as the system design phase of a development project. Ruth agreed with your recommendation and has asked you to go forward with the plan.

ACTIVITY 7
1. Review the EOF fact-finding summary and all other information you have about the required system and critically analyse this for duplications and inconsistencies.
2. Draw an ERD or domain model class diagram with crows-foot cardinality notation. Assume that system entities include farms, customers, status as Regular or Variable, orders, vegetables with associated price per unit, and delivery person (at minimum).
3. Design tables - making sure each table only refers to one "thing". As you create the database design, identify primary and foreign keys by underlining primary keys, and making foreign keys italic.
4. If you add primary keys which use codes - for example a code for the farmID, then identify the format of these codes.
5. Create suitable sample data to populate the fields for at least three records in each table.
6. Include the following in your report:
• The ERD or domain model class diagram you have completed;
• The database design (schemas);
• Formats of codes used;
• Sample data for each table.

CASE STUDY 8

You are now making sure that you have sufficient models to understand the new system. In reviewing the models (use-cases diagrams, including activity diagrams) you realise that you have not included a system sequence diagram for any of the use cases.
After creating this, you are now ready to review the options for a new system, and make a recommendation to Ruth and Ian.

ACTIVITY 8

1. Create a system sequence diagram for one of the use cases identified in Activity 6. Add this system sequence diagram to your report in the appropriate area.

2. Search online for potential commercial software packages for "Eat Organic Food. Identify two packages, and compare their features, and their suitability to be used as the new system.

3. Present at least three options for the new system in your report. One of these must be in-house development, and two of the others may be the commercial packages as identified in (3) above.

4. Review your feasibility analysis for the new system. Taking all options into consideration, make a recommendation for the new system, in your "Conclusion and Recommendations" section.

FINALISE YOUR REPORT
You have completed the contents of your report, and now need to make sure that the report is presented professionally, as it will be shown to Ian, Ruth and owners of farms intending to work with "Eat Organic Food, as well as any potential investors in the new system, and the expanding prospects for "Eat Organic Food.

ACTIVITY 9
Ensure your report is professionally presented. This means your report should include:
• a title page, with the name of the Report, and the analyst's name (your name);
• an executive summary;
• a table of contents, with page numbers;
• page numbers on all pages except the title page;
• Headings, sub-headings, dot-points and numbering where necessary. Headings should be numbered or the structure should otherwise be easily identified;
• Appendices where necessary;
• Formatting and whitespace (space where there is no text or pictures) used appropriately; (Be willing to start each new section on a new page);
• Page orientation used appropriately. For example, if you have an ERD that will show better in landscape orientation than portrait orientation , set a Section break (Page Layout
> Breaks) before this page, set the page to landscape and then set another Section break to start the new page in portrait again.

Attachment:- TEMPLATE_REPORT.rar