BIS 450 DeVry Course Project
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>BIS</strong> <strong>450</strong> <strong>DeVry</strong> <strong>Course</strong> <strong>Project</strong><br />
Downloading is very simple, you can download this <strong>Course</strong> here:<br />
http://mindsblow.us/question_des/<strong>BIS</strong><strong>450</strong><strong>DeVry</strong><strong>Course</strong><strong>Project</strong>/4398<br />
Or<br />
Contact us at:<br />
help@mindblows.us<br />
<strong>BIS</strong> <strong>450</strong> <strong>DeVry</strong> <strong>Course</strong> <strong>Project</strong><br />
<strong>BIS</strong><strong>450</strong><br />
<strong>BIS</strong> <strong>450</strong> <strong>DeVry</strong> <strong>Course</strong> <strong>Project</strong><br />
<strong>Course</strong> <strong>Project</strong> > Objectives What's this?<br />
Objectives<br />
Throughout this course, you will be developing the specifications for a web-based solution to a business need. As you<br />
do so, remember to incorporate the tools and techniques you learn in this class into your proposal. You won't actually<br />
be creating the proposed project in this class, so think big and imagine all the possibilities! The kind of project that you<br />
are proposing might require three or four programmers and many months of development and testing time.<br />
You will complete parts of this project each week as you go through the course, starting in Week 1 with an overview of<br />
the business situation you are addressing. Your instructor will provide you feedback and you will need to incorporate<br />
this feedback into your project. After completing most of the required sections in class, you will then incorporate them<br />
into the final report, which will summarize your proposal and add a few additional sections. This project takes the place<br />
of the Final Exam in this course, so you are expected to work on the final version of your proposal during Week 8. Your<br />
instructor will provide you with the exact time the project is to be delivered to the Week 8 <strong>Course</strong> <strong>Project</strong> Dropbox.<br />
The organization you are crafting a solution for can be real or imagined. If you'd like, you can look at an existing solution<br />
as a starting point, such as virtual supply chain management software. In this case, you'd want to think about what you<br />
could do to extend that application. Creating a solution from scratch is fine as well, as each approach has its<br />
advantages. Starting with an existing solution helps you to model data and system use, which isn't as straightforward<br />
for a complex system as it is for say, a shopping cart on a website. If you are interested in systems analysis or working<br />
with larger, complex, business-internal processes, this is the correct path to choose. On the other hand, if you are<br />
interested in creating a customer-facing entrepreneurial venture, then chances are you'll need to envision the basic<br />
business processes involved from the ground up, and they might even be novel processes. You have a lot of flexibility<br />
to work with in this <strong>Course</strong> <strong>Project</strong>.<br />
<strong>Course</strong> <strong>Project</strong> Milestones<br />
Assignments Points Due<br />
Overview of Business and Web-Based Solution 35 Week 1<br />
Server-Side Technology 35 Week 2<br />
Interface and Processing 35 Week 3<br />
Database Structure 35 Week 4<br />
Security and Mobile Devices 35 Week 6<br />
Deployment and Testing 35 Week 7<br />
Final <strong>Course</strong> <strong>Project</strong> 170 Week 8
Guidelines<br />
The Week 1 Assignment should consist of the following section:<br />
Overview of Business and Web-Based Solution (1–2 pages)<br />
Describe the business (real or imagined) involved thoroughly. What is the industry? What is the revenue model? What<br />
is the company's strategic vision and who are the stakeholders? Do they produce goods, services, or both? How are<br />
the products distributed and what operations strategy is involved? Who are their competitors and how does their<br />
business differ from the company you are describing?<br />
Describe the web-based solution to the situation. In this section, only a general description is required, but some things<br />
to include would be how many visitors per month would be expected, how much downtime on the server could be<br />
acceptable, what are the data storage needs, and what general processing needs will be required.<br />
The Week 2 Assignment should consist of the following section:<br />
Server-Side Technology (1–1.5 pages)<br />
Based on what you have learned in the course, which technology platform would you choose, and why? Remember<br />
that although we are using ASP.NET for this course, developing in Visual Basic, and using Microsoft Access as our<br />
RDBMS, this solution does not work in every circumstance. You might choose to use an open source solution, such as<br />
LAMP (described in the lecture) if your company has a reduced budget. You might upgrade to Oracle and multiple web<br />
servers if you need massive scalability. You might also choose to have a small site hosted by an external hosting<br />
company.<br />
You should create a cost estimate of the required technology platform. Make sure to include licenses for your server, if<br />
required (IIS), physical hardware components (your server machine), a static IP address, your domain name, any<br />
security issues, licenses for your web application platform (e.g., ASP.NET), your database server (e.g., Oracle), and<br />
your development time (how many developers at what salary for how many months).<br />
The Week 3 Assignment should consist of the following section:<br />
Interface and Processing Required (2–3 pages)<br />
What does your user interface look like? What components are required? Are there buttons, dropdown menus, labels,<br />
and so on? How is database data presented—as a table or a form? Is the application available from the home page,<br />
or do users have to navigate to it? What does your navigation structure look like, and what colors are featured on the<br />
site? Make sure to include a mock-up of your main interface screen. This can be done in a tool such as Visio, or you<br />
can create it by dragging and dropping components inside Visual Studio and then creating a screenshot. Hand-drawn<br />
sketches are not acceptable in your final report.<br />
What is the main processing routine required by your site? Describe it in detail and include a chart showing the input,<br />
processing, and output (IPO). You should probably make this in Visio, but any other drawing tool is fine as well if it can<br />
create the required shapes. As an example, imagine adding customer information to a database. The input required<br />
includes a first name, a last name, a zip code, an e-mail address, and so on. The processing that needs to occur is that<br />
the system needs to check whether or not that customer already exists, and if the data that they have entered is valid<br />
(e.g., zip code can't equal "Mars"). If all is well, the information gets entered into the database. The output generated<br />
would be a confirmation that the address was successfully added, or a rejection of the submission. Remember to always<br />
provide output to your users, it lets them know the results of their interaction with your system, even if it's a simple<br />
yes/no answer. Note that here you need to describe the main processing routine for your system.<br />
The Week 4 Assignment should consist of the following section:<br />
Database Structure Requirements (1 page)<br />
What requirements do you have for your database? You have already specified which platforms you are going to use<br />
in the first section of the document, so there's no need to repeat that here. You do need to answer the following<br />
questions, however. What tables will your database include? What are the primary keys for each? Which fields are<br />
included for each? What are the data types and field sizes for each field? What validation will be done at the database<br />
level? What are the table relationships? Include a chart showing the tables and their fields; you can create it in Visio or<br />
by building the table in Access and getting a screenshot. Note that a chart by itself does not fulfill the requirements,<br />
and hand-drawn sketches are not acceptable in your final project.<br />
The Week 6 Assignment should consist of the following section:
Security and Mobile Devices (2–3 pages)<br />
What are the business needs for the security of your site? Are you in a regulated field like finance, healthcare, or<br />
education? What are the legal security requirements for protecting data and the privacy of your users? How will you go<br />
about securing your site? Will you obtain a digital certificate? Will you use HTTPS protocol? How will you physically<br />
secure your server? What is your backup plan, and how will you assure business continuity in the event your server is<br />
damaged or destroyed? Where will the server be kept and who has access to it?<br />
What mobile platforms will access your site? Will you try for maximum compatibility across all platforms, or require<br />
particular mobile devices or kinds of devices to be used? What elements of your site will you discard for mobile users,<br />
and which will you prioritize? What percentage of mobile users do you actually expect to use your site versus desktop<br />
users? What about laptops and tablet computers?<br />
The Week 7 Assignment should consist of the following sections:<br />
Deployment and Testing (1–2 pages)<br />
How will you deploy your site? If you are replacing an existing system, will you simply turn off the old system when the<br />
new one is ready? Do you have to transfer your application data to a server? How would you go about doing that? How<br />
do you get a static IP address and configure your machine to use it? How do you activate your backup system?<br />
What testing will be performed on the application before you deploy it live? What limit cases could you use for data?<br />
What data would you expect to fail your validation testing? What use cases will you consider—what user profiles would<br />
you expect to visit your site? Include at least three different scenarios for use of your site.<br />
The Final <strong>Course</strong> <strong>Project</strong> must include updated and corrected versions of all the sections listed above, plus the following<br />
new sections:<br />
Summary and Conclusion (1 paragraph each)<br />
In summary, what is the problem and how do you propose to address it? Precisely and succinctly summarize your<br />
proposal in one small, neat paragraph. Please note that this is not the time to add or discuss new features or ideas. A<br />
summary restates what has been described previously in the paper. It is designed to be redundant. You already know<br />
the contents of your paper, but your reader may not, and he or she may be skimming ahead. The summary is for his<br />
or her convenience, not yours.<br />
What is your conclusion? Again, a conclusion is not a time to add or discuss new ideas. It's the time to state that your<br />
solution can be implemented for so many dollars and labor hours and parts, and it will address the need that you have<br />
identified previously and the proposed solution. If you complete this section correctly, the conclusion will be apparent<br />
because you have set it up in the previous paragraph; yet, you need to make it clear that what you propose will<br />
adequately address the problem. Watch out for overreaching and hyperbole. You aren't creating a be-all end-all for the<br />
Internet or pushing the boundaries of technological evolution. You are proposing a well-considered, modest, web-based<br />
solution to a business problem or situation. You should acknowledge there are other possible solutions that can be<br />
considered as well. A good business argument comes from rational choice among logical possibilities. You have made<br />
the case for one possible implementation, but ultimately, you should be prepared to accept that your proposal might be<br />
one of many.<br />
Grading Rubrics<br />
Grading Rubric for Weeks 1–4, 6, and 7 Submissions<br />
Category Points % Description<br />
Documentation and Formatting 7 20% Follows correct APA format. Overall appearance of the document is clean,<br />
readable, and professional. Statements are supported, as needed, by credible, authoritative industry or academic<br />
sources. Sources are cited as in-text citations with full information on each source in the reference list.<br />
Editing, Organization, and Cohesiveness 7 20% Writing is clear, readable, and professional; free of errors in spelling,<br />
grammar, and punctuation. There is a logical flow of ideas within each section and across sections. There is a<br />
consistent, unified view of the proposed system.<br />
Content 21 60% All required information for the section is presented as per the guidelines above. Any required charts<br />
or tables are present. Contents are clear, specific, and technically accurate.<br />
Total 35 100% A quality paper will meet or exceed all of the above requirements.<br />
Grading Rubric for Final <strong>Project</strong> Report in Week 8
Category Points % Description<br />
Documentation and Formatting 34 20% Follows correct APA format. Overall appearance of the document is clean,<br />
readable, and professional. Statements are supported, as needed, by credible, authoritative industry or academic<br />
sources. Sources are cited as in-text citations with full information on each source in the reference list.<br />
Organization and Cohesiveness 17 10% There is a logical flow of ideas within each section and across sections. There<br />
is a consistent, unified view of the proposed system.<br />
Editing 17 10% Writing is clear, readable, and professional; free of errors in spelling, grammar, and punctuation.<br />
Content 102 60% All required information for the section is presented as per the guidelines above. Any required charts<br />
or tables are present. Contents are clear, specific, and technically accurate. Summary paragraph adequately<br />
summarizes the paper. Conclusion ties summary to financials and includes a recommendation for implementation.<br />
Total 170 100% A quality paper will meet or exceed all of the above requirements.<br />
Best Practices<br />
Page counts are outlined in each assignment milestone.<br />
Assignments should follow APA format (title page, in-text citations, reference page, font type/size, spacing, paragraph<br />
indentation, etc.).<br />
Do not use clip art anywhere in the assignments, not even on the cover page.<br />
No more than two spelling or grammar mistakes are allowed throughout the entire paper. More than this will result in a<br />
point deduction.<br />
Incorporate feedback from your instructor into future assignments and the final project.<br />
Do not leave any isolated headings at the bottom of a page.<br />
Adhere to Standard Edited American English.