Small System SDLC Design/Plan Project- Final

profilevbkngl
projectsandpapersifsm310spring2015ol4.docx

IFSM 310 Spring 2015

Projects and Written Papers

Trouble with links?

If linking to these instructions from elsewhere in LEO fails, then remember that: (a) the individual assignments can be found in LEO Content > Week n > Week n Graded Assignments and Activities > then the individual project assignment document; and (b) this consolidated compilation of all project assignments can be found in LEO Content > Course Content > Projects Information.

Contents

General Paper and Writing Requirements 1

Product Survey Project 4

Small System Design Project 6

General Paper and Writing Requirements

This applies to all projects and papers except where noted.

File Names

The files submitted should be named as follows: Your last name and project title. For example: "Schank DraftPlan.docx".

All assignments are to be submitted in your Assignments Folder.

Format

Format is APA style, which means and includes the following:

· Use Microsoft Word. If you do not have Microsoft Word, "Save As" a Word document in .doc or .docx format.

· Use Page Setup to configure it.

· Use 1" margins top, bottom, left and right sides.

· Use Times New Roman or Calibri size 12; or Arial, or Verdana size 10.

· Line spacing should be no more than 1.5-spaced.

· Use appropriate paragraph and section headings and subheadings. Headings and subheadings should be placed at the left margin.

· The first word of each new paragraph should be indented.

· For documents that are longer than one page, number each page in the bottom right corner. The title page should not be numbered.

· Size limit: A page limit and number of words are specified in the instructions for each project or paper. The limit refers to the body of the paper excluding the "front matter" (title page, table of contents, executive summary) and "back matter" (reference bibliography of works cited). The body of the paper should be neither shorter than the lower limits not longer than the upper limits. Exceeding the upper limit may result in a deduction.

Title Page

Use an un-numbered title page as the first page of the document. Use whatever font, color, and type size you prefer. In the center of the page, double spaced, put:

· Your name

· The name of the project itself (e.g., "Product Survey" or "Small System Design DRAFT")

· IFSM 310-7980: Hardware/Software Infrastructure Architecture

· Your title for the paper (e.g., "Our Town Urgent Care Facility")

· The date

· You may add optional clip art or graphics if desired. It is not required and will not earn any additional points.

Nothing else needs to be added to the title page. Remember, the title page is not a separate document. It is the first (unnumbered) page of your document and does not count in the page size requirements.

Front Matter

For Draft papers, a table of contents and executive summary are optional.

Final papers should include a MS Word-generated table of contents; the kind that has hyperlinks to click on to get to the corresponding sections of the document. (If you need assistance in doing this, use MS Word's Help; instructions are also available in Course Content under "Supplemental Materials" or at Creating "Automatic" Clickable Tables of Contents in MS Word.)

Final papers should also include a 1/2- to 1-page Executive Summary that summarizes the purpose, approach, and conclusion of the document. (Again, if you need assistance, see Course Content "Supplemental Materials" or Tips on Executive Summaries and The secrets of writing a truly useful executive summary.)

Writing Quality

Unless otherwise noted, the written papers will be graded in part (≈30%) on format, style, and writing quality. The remainder (≈70%) will be based on substance, content, accuracy, and correctness.

Writing quality includes considerations such as (but not limited to) the following:

· Grammar, verb tenses, pronoun use, spelling, punctuation, and writing competency.

· Spelling. Remember to spell-check, and then to proofread. Better yet, have a friend or colleague read it before submitting it. Read it out loud to yourself. It’s amazing how many mistakes we find when we read out loud. This is because we are forced to slow down and LOOK at the words.

· In a professional paper one does not use contractions ("doesn't," "don't," etc.) and one does not use the personal pronouns "you" or "your". Although there may be some exceptions, it is preferable to not use the first person ("I," "me," "my," etc.).

· In a professional or academic paper in the US, companies and organizations should be referred to as “it” not “they.” (It's true that this is done differently in Britain, but we are an American university.)

· Use references -- in APA format – (in text citations and Reference pages) even if you have all the information in your head. References add credibility to your work , provide sources for the reader to find more information and lend academic credence. References show the professor that you did above and beyond what was required in order to produce a high quality deliverable.

References

Use the APA format for references and citations. Use a Reference List page as a list of works cited, as the last page of the document. Remember that the Reference page ONLY includes sources that you used in the text. APA format does NOT use a “bibliography”; only a Reference Page. If you are unsure of format, please review the APA tutorial in the Course Content area of our WebTycho classroom, or go through the UMUC ILS library website for other help and assistance, or contact the Effective Writing Center.

Your sources should be either scholarly or industrial. That is, they should come from scholarly papers found in ILS's research databases, from Google Scholar, from libraries, etc. Or, if referring to commercial products, they may be references to the company's Web site, white papers, user manuals, brochures, and similar materials. Wikipedia and other encyclopedias should not be used as a reference source (see below).

References and in-line citations go together. Neither is complete without the other. Your paper must also include in-line citations to the references in the "back matter" page. There should not be an in-line citation without a corresponding source in the reference page, and there should not be a source in the reference page that is not used or cited in-line in the body of the paper. For instructions, see the APA tutorial and other materials mentioned above.

Other Requirements

Original work. All papers must be your original work, in your own words, and written for this class. Do not simply copy/paste information from the Web or textbook. Such submissions will not be accepted for credit. Research projects should be original work for IFSM 310; therefore, you may not re-use of a paper written you’ve written for a different class.

Wikipedia. Wikipedia is useful for background, but it is not a scholarly source and may not be used in your references. Sometimes, Wikipedia can point you in the right direction and can suggest other sources that can be obtained in ILS's research databases, such as scholarly papers, or can point you to manufacturers' explanatory materials. However, Wikipedia articles and other encyclopedia articles should not be used as a reference source.

Templates, etc. Use of outlines, examples, and templates that you may find (including those in textbooks) is acceptable for the structure and outline of some assignments. However, the substance of all assignments must be your own original work and must include proper quotation, citation, attribution, and bibliography of sources and works used.

Product Survey Project

Product Survey is due date is posted in the Weekly Conferences and Class Announcements

Post your submission into your Assignments Folder and I'll provide my feedback there.

You will use the theoretical studies of computer hardware and software (SW) and apply them to a study of real-world IT products. Using descriptions of computer hardware and software components from course lessons and the textbook, you are to write a 700 to 1000 word (no more than 1.5 line spacing and no more than 12 point type) summary of the hardware and software products that would be required for a small system for either a financial investment or architectural firm (your choice).  You have a budget of $6,000.  Be sure to include any specialized software in addition to the OS and Office productivity SW, anti-virus / firewall / physical security, address Internet connectivity, storage, and hardware components required. You will  

a. discuss why you have chosen each component;

b. list the make and model of each component;

c. list what the manufacturer indicates as benefits of the products;

d. list how much the products cost - include a summary table with the total system cost;

e. compare the major hardware and software selections to at least two other manufacturers' products

(i) Note: software for the investment firm should not be an accounting tool - you are helping clients decide how to invest their money;

f. include security for the system; and 

g. include references for your costs to document how you stayed within your budget. 

You are encouraged to use the Web to research and select the component products and contact the vendor directly with any questions.

Grading: This activity is awarded 10 points towards the total grade in the course.  

Attributes

Value

Description and justification of software requirements

2 points

Description and justification of hardware requirements

2 points

Manufacturer source information (benefit and cost)

2 points

Comparison between manufacturers

2 points

Readability, Style, Mechanics

2 points

 Detailed elements of grading rubric:

Score

Each of the above elements will earn …

Criteria

90-100% of the maximum possible for the element, when …

All required elements are present. Content is complete, and demonstrate mastery of concepts, skills, etc. Performance and results above and beyond standards and requirements.

80-89% of the maximum possible for the element, when …

All required elements are present. Content demonstrates competence in concepts, skills, etc. Content is substantially complete. Performance and results generally exceed most standards and requirements

70-79% of the maximum possible for the element, when …

Major required elements are present. Content is substantially complete and demonstrates understanding of concepts, ability in required skills, etc., with few exceptions and minor incompleteness. Performance and results meet standards and requirements

60-69% of the maximum possible for the element, when …

Major required elements are missing. Content is incomplete, or incorrect or demonstrates lack of understanding of concepts, lack of ability in required skills, etc. Performance and results do not meet standards and requirements (No answer or response at all earns zero points, as does a response with evidence of plagiarism.)

Small System Design Project

(Draft due Wk 5, Final paper due Wk 8)

Draft Due date is posted in the Weekly Conferences and Class Announcements

Final Paper Due date is posted in the Weekly Conferences and Class Announcements

You will use the information learned throughout the course to identify and document a full information system for a small company. You will apply the basic steps of the SDLC (Systems Development Life Cycle) to design and implement the IT infrastructure for an electronic health care data system for the (mythical) “Our Town” urgent care facility* by addressing what actions are taken and what decisions are made in each phase.

Make sure to address key technical issues from this course and to include and specify key elements and components of a computer system as covered in this course, including (but not limited to) the following (in no particular order):

· HIPAA compatible EMR software*

· While you could design your own application, it’s acceptable (and recommended) to search, compare, and select an existing package from the Web

· Hardware that supports the EMR:

· CPU type, speed, etc.

· Memory type, size, speed, etc.

· Desktop or mobile

· In house or cloud based system

· Networking

· Operating system

· Other required software

· I/O devices (i.e., peripherals)

· Shared resources

· Storage; backup; disaster planning

· Physical and electronic Security*

· Privacy*

· While you could design your own application, it’s acceptable (and recommended) to search, compare, and select an existing EMR from the Web

· Be sure to include a network diagram

The body of the paper should be no more than 12 point type, not less than 4 pages or 1200 words and not more than 8 pages or 2400 words, not including title page, table of contents, executive summary, and reference bibliography. The paper will require a title page, a hot-clickable MS Word generated table of contents, executive summary, 4-8 pages of content with incorporation of a minimum of 3 external resources from credible sources, and a Works Cited/Reference page.

Use the SDLC to help organize the paper and use its steps to show how the requirements, design, implementation and testing are accomplished. However, the emphasis of the paper must be on the technology outcome and how it flows from the functional requirements.

Refer to the document "SDLC Module 2 from IFSM 201" and other SDLC material in Course Content. 

You have a free hand here - design the office you'd like to go to if you need medical care. Specify the key features of the facility: layout of the office (i.e., number of employees and their roles to determine the number and type of systems needed), which Electronic Medical Records software you'll choose, the necessary hardware, an understanding of the regulations you need to comply with, and how you'll implement and test your design. The paper should make clear how the functional requirements of the clinic result in the specific technical design specifications, above.

Remember that there are many variants of the SDLC other than what is presented in the above module. You may use any variant of the SDLC that you wish provided that (a) it is logical and complete (and not pulled out of the air), (b) it is appropriate for the system you are designing in your paper, (c) you identify which variant you are using, and (d) you include each step.

Make sure your paper identifies which approach you will employ, but clearly articulate the steps used to:

1. Complete a preliminary investigation, requirements analysis, and system recommendation

2. Specify a detailed design based on your set of requirements.

3. Develop the system according to your design specification.

4. Outline how you would test the system and gain user acceptance.

In your submission, be sure to include any references used in APA style (see the tutorial in the COURSE CONTENT menu) for your source information in a bibliography as well as cite them within the body of your paper.  Be sure to check your work for spelling and grammatical errors before submission.  Yes, spelling and grammar count. The intent of these topics is to provide you with an opportunity to hone your writing skills. 

The paper must be your original work, in your own words, and written for this class. Do not simply copy/paste information from the Web or textbook. Such submissions will not be accepted for credit. Research projects should be original work for IFSM 310; therefore, you may not re-use of a paper written you’ve written for a different class.

All "General Paper and Writing Requirements" for all papers (above) must be adhered to for this assignment, except as specifically noted (e.g., table of contents is required, page limits are 4-10 pages, etc.).

Remember that in accordance with the policy in the Syllabus, students must submit the Final paper (not the draft) to http://turnitin.com/ and must attach the TurnItIn "Originality Report" to the submission in the Assignments Folder along with the paper itself.  Draft papers and topic selection (DraftPlan) need not be run through TurnItIn. 

ClassID: 9592015

Password: validpaper

Remember that the correct TurnItIn report to submit is the Originality Report , not the Digital Receipt.

--------------

* (Note that since this is a medical facility, your design should comply with Congressional regulations. Since 1996, the Health Insurance Portability and Accountability Act (HIPAA) details patient privacy and regulations for health care-related businesses. In addition to HIPAA, there were two acts passed by Congress in 2009 that specifically garnered support for migrating to electronic medical records (EMRs). The Health Information Technology for Economic and Clinical Health (HITECH) Act is specifically geared at providing financial incentives to health care organizations that migrate towards EMRs, with the intention of eventually replacing the incentives with penalties if providers do not institute electronic record keeping. The second is the American Reinvestment and Recovery Act (ARRA), which institutes funding for comparative effectiveness research (CER). Analysis and aggregation of anonymized patient data in regards to conditions, treatment and progress can provide an invaluable source of CER to physicians and healthcare organizations in the treatment of patients.

Therefore, privacy and security requirements must be addressed. However, computer architecture and system design are the primary subjects of this course and will be more important in the grading than the nuances of Federal law, privacy, and security. It would therefore be a mistake to take so much time researching and designing for health care privacy and security laws that your hardware and software infrastructure suffered as a consequence.

You may want to incorporate tables of technical specs, as that is often a more effective way than narrative paragraphs for presenting them. Also, if you can, please try to draw a diagram of the system, either of its internal architecture and/or of its external connectivity, as appropriate.

Submission and Grading

Draft Paper

The Draft is due date is posted in the Weekly Conferences and Class Announcements

The requirements for the draft paper are the same as for the final paper, with the following exceptions.  For the draft:

· The table of contents and executive summary are optional. 

· (The reference page is required for both draft and final.)

· The page and word count limits are relaxed for the draft.  Just keep it fairly reasonable -- not trivially short and especially not too long. (For the final paper, the page and word count limit will be as specified above.)

· As the intent of the draft is to ensure that you are on the right track and to offer advice on improving the paper before final submission, the grading for the draft paper will be more lenient than the grading for the final paper. 

· The grading elements, however, will be essentially the same.

Submit both the draft and final papers into your Assignments Folder.

Final Paper

The final paper due date is posted in the Weekly Conferences and Class Announcements

Submit both the draft and final papers into your Assignments Folder. Use track changes or highlight the changes you made resulting from the feedback received from the draft.

This paper earns 20% of the final course grade. The weight toward the course grade will be 5% for the draft and 15% for the final plan.

Grading rubric -- 15 points toward course grade for final paper; 5 points for draft

Format, structure, style, and mechanics: approx. ≈20%

Content and substance: approx. ≈80%

Detailed elements of grading rubric:

* Format, structure, style, and mechanics

20%

Title page;

Font and Spacing;

Page length and word count;

Table of contents;

Executive summary;

APA In-text citations;

APA Reference List (bibliography);

Organization and style;

Grammar, correctness, spelling;

* Process and Detailed Design

30%

Concept Investigation, Planning, Requirements Analysis, Problem Statement;

Business Requirements / Establishment of Need;

Facts, Assumptions, Constraints;

Systems Analysis, Problem Investigation;

Analysis of Alternatives;

Systems Design;

Construction, Development, Building, Programming;

Verification, Testing and Training;

System Implementation;

Disaster plan;

System Maintenance

* HW-SW Design Components

50%

Processor / CPU (w/ specs); incl. cache, bus, graphics processor / card, etc., for desktop and mobile devices; Identify specific manufacturer(s)

7%

Primary Memory / RAM (w/ specs)

3%

Storage; incl. Secondary storage / disk (with specs); Tertiary / removable storage / backup storage; virtual memory; etc.

5%

Networking; incl. Network Interface (NIC or Wireless card); Server; Broadband modem & ISP / Internet connection; System Networking HW (LAN/router/gateway/switch); Network topology; Network protocols; Network Diagram

10%

I/O and peripherals

3%

Operating System; incl. OS Type and Characteristics; File Management; Utilities;

3%

HIPAA compatible EMR Software with explanation as to why it's appropriate for your application

5%

Security; incl. Software (A-V, firewall, etc); physical, privacy considerations (role based access to comply with HIPAA)

5%

Evidence of Requirements and analysis leading to specified design

9%

Score

Each of the above elements will earn …

Criteria

90-100% of the maximum possible for the element, when …

All required elements are present. Content is complete, and demonstrate mastery of concepts, skills, etc. Performance and results above and beyond standards and requirements.

80-89% of the maximum possible for the element, when …

All required elements are present. Content demonstrates competence in concepts, skills, etc. Content is substantially complete. Performance and results generally exceed most standards and requirements

70-79% of the maximum possible for the element, when …

Major required elements are present. Content is substantially complete and demonstrates understanding of concepts, ability in required skills, etc., with few exceptions and minor incompleteness. Performance and results meet standards and requirements

60-69% of the maximum possible for the element, when …

Major required elements are missing. Content is incomplete, or incorrect or demonstrates lack of understanding of concepts, lack of ability in required skills, etc. Performance and results do not meet standards and requirements (No answer or response at all earns zero points, as does a response with evidence of plagiarism.)

Projects and Papers IFSM 310-6380 Spring 2013.docx

12 of 12