Dibatalkan

Managment Support Systems Report relating to case study

Each member of the team should make a different selection from the range of management decisions in the case study. If two team members do decide to use the same decision, this must be justified in section 9, and there must be no overlap in the queries/reports and spreadsheets, although there should be cross-referencing to indicate whether the solutions complement each other, and how they could be used in conjunction with each other.

9. Selected Management Decision (up to 1 page)

Identify and briefly discuss the Officionado management decision selected:

· identify the stakeholder(s) for this decision and their critical success factor(s)

· outline the information requirements of managers making this decision

10. Data and Information Requirements (up to 2 pages)

Identify the data required to support the decision, including specific entities and attributes in the ODDS database, and any other data, such as external sources. Explain why any additional data has been added to the database, and its source. Outline the transformation processes required to convert data into information needed by decision maker(s). Consider: aggregation, calculation, classification, selection, sorting, summary.

11. Technical Design (up to 2 pages)

Present the technical details of the solution design, clearly identifying the data it uses and explaining how this data is transformed to produce useful information. This section should make use of one or more recognised design technique(s), e.g. Decision table/tree, STD, ERD, DFD, task analysis, flow chart, any UML techniques, etc.

12. Test Plan and Results (length depends on complexity of the application; up to 5 pages)

Provide a detailed and practical test plan. The bulk of this section should be in the form of a table detailing specific tests that have been conducted (Test Number, Condition, Input Required, Expected Outcome, Actual Result, Modification Undertaken, Comments, etc.). Provide a brief commentary, explaining how the results of testing were used to amend the design and/or implementation of the ODDS MSS.

13. Outline Solution (up to 2 pages)

Describe the MSS solution in business terms with any relevant illustrations (diagrams and screen shots from the ODDS MSS application). This section should include a brief practical justification of the ODDS MSS solution for each decision, identifying the key stakeholders and specifying the benefits this application will offer.

14. References (Group and Individual)

Use the Harvard Referencing Style to indicate details of books, case study material, documents, journal papers, websites, etc. cited in the report. There should be a single section of references covering all material used in the group and individual components.

The software will include the following:

15. Software with printouts

(software on CD/DVD/USB stick; up to 2 pages per query/report and charts/graphs)

The software submitted on CD/DVD/USB stick should include:

· a version of the Access or Oracle database with

- a menu (switchboard) or other suitable interface to facilitate user interaction;

- 3 parameter-driven queries/reports

· an Excel application using data downloaded from the database, providing dynamic functionality and using charts/graphs to illustrate trends/patterns in the data.

The printouts should show output generated by ODDS in the queries/reports, and the charts/graphs produced to support the chosen management decision.

· Provide three database queries/reports providing information relevant to the decision selected by each team member. Give clear instructions on how these are used.

· Provide a worksheet in a spreadsheet to produce charts/graphs.

Kemahiran: Oracle, Penulisan Laporan, Penulisan Penyelidikan , SQL

Lihat lebih lanjut: why use use case diagrams, why use graphs, why are graphs used, user case diagrams, use case include, use case diagrams in uml, use case diagrams include, use case diagrams for websites, use case diagrams, use case components, uml use case uses, uml task, uml for sql, uml diagrams use case, uml application design, uml and use case diagrams, tree range, tree query, tree graphs, technical support websites, systems analysis and design, sql to oracle, sorting complexity table, solution design group, software testing techniques

Tentang Majikan:
( 0 ulasan ) London, United Kingdom

ID Projek: #4038280

5 pekerja bebas membida secara purata $200 untuk pekerjaan ini

swiftcult22

hello sir. Strong and constant communication will enable us both to comprehend what you actually require and what i will give you in the form of assignment i don't say "pick me" but can state assertively that give me a Lagi

$250 USD dalam 5 hari
(210 Ulasan)
7.2
softxpress

Hi, you can consider this project completed as per your requirements. I can really meet your expectations and willing to work on it whole heartedly. Kindly have a look at PMB. Thanks

$200 USD dalam 5 hari
(132 Ulasan)
6.5
imranhossain

Hello sir, Greetings!!!Right person is here according to your requirement. I'm constantly providing great, highly informative, analysis where necessary, great and quality papers, essays, reports, case study, dissert Lagi

$200 USD dalam 7 hari
(93 Ulasan)
6.2
samin59

You think about quality, we deliver it. Please check PM.

$200 USD dalam 4 hari
(56 Ulasan)
5.4
rafaelnadal

Hi, thanks for your project. More details on my bid are in your inbox. I will try my best to provide best possible quality.

$150 USD dalam 3 hari
(28 Ulasan)
4.7