ITM 602: Enterprise Application Development
WEEKLY PROGRESS REPORTEach group is responsible for a weekly progress report, in which they detail achievements and issues. There are two different documents: one for business plan development (Weeks 1-6) and the other for implementation of the final product (Weeks 7-14). These documents should be continually updated and emailed to BOTH instructors by the end of each week at email@example.com and WBrigham@uamail.albany.edu.
BUSINESS PLAN ASSIGNMENTSAll of these assignments will assist in the creation of the final business plan. All weeks besides the first week, groups are expected to show their work and discuss their ideas briefly with the instructor at the end of the class and email the templates to BOTH instructors. This will give an opportunity for an intermediate review before the final business plan presentation and review grading.
Week 1: Idea GenerationAll of the members of your group should develop one web-based service/product idea with a description as well as a contact list with a schedule of times when each member would be available/not available. Decide on the two best ideas (one for the main idea and another as a backup). Detail preliminary reasons why you chose these two.
Week 2: Feasibility Analysis & Financial PlanBased on the two plans chosen, do a thorough feasibility analysis and preliminary financial plan for each. The feasibilty analysis and financial plan should assist in determining what is the best idea to implement.
Week 3: Human Resources & MarketingBased on the final plan chosen, develop a human resources plan, competitive analysis, market analysis, and marketing plan.
Week 4: Presentation & ReviewPlease refer to the Projects/Papers section of the course site to get guidelines on the presentation and the final business plan project.
Week 5:Final Business Plan SubmissionPlease refer to the Projects/Papers section of the course site to get guidelines on the final business plan requirements.
IMPLEMENTATION ASSIGNMENTSHands-on code development experience is critical to your success in understanding the complexitities in developing enterprise application systems. There will be a number of an assignments related to code and database development in the second part of the class. These assignments will typically be components of the projects and help you consolidate your learning as well as take you forward in your projects. It is important for the material in these assignments to be as accurate as possible and as close to your final design since you will use these initial assignments as building blocks for completing later assignments. A lot of rework will slow you down and lead to inefficiencies.
Please submit programming assignments electronically and for a group assignment, only one e-mail should be submitted.
Week 6: Logical Database Design (ERD)Create an entity-relationship diagram for your service. This is usually where students end up making mistakes and then need to redo later tasks such as SQL queries, database creation, etc. It is essential that you really think about this assignment.
Week 7: Database Creation + SQL QueriesIn this assignment, first create a data definition table. This will assist in the second part of the assignment which is creation of SQL queries which you believe will be used in your online service.
Week 8: Web InterfaceCreate two different protoypes on paper, and then determine what elements from each is preferred to create a template using HTML or XHTML.
Week 9: Choreography (Use Cases)Think about what functions will be necessary in your online service. Create a use case for each of these functions.
Week 10: ServletsFor this assignment, create a servlet for authenticating users. It is anticipated you will need more servlets for your online service, but for this assignment only copy the servlet code for authentication.
Week 11: Study for ExamThe exam will be towards the end of the class. It is advisable to bring a pencil so that you can easily make changes. The exam will be composed of questions which include those on design documentation, programming, and architecture. The understanding of concepts will be more important than of actual syntax when being considered for grading. Please refer to the Grading section of the course site to get guidelines on exam details.
Week 12: PrototypeStudents will prepare a demonstration for feedback from the instructor and should be prepared for an individual code review. It is anticipated that students will nearing completion of their systems.
Week 13: Final Presentation and Project ReviewPlease refer to the Coursework section of the course site to get guidelines on the implementation final presentation and project review.
FINAL BUSINESS PLAN & PRESENTATIONThe fifth class is a chance for everyone to present their business plan to an evaluation committee (Chamber of Commerce). This committee, in addition to the instructor(s) are responsible for the grading of the project. The project grade will be a collected grade from the initial presentation and executive summary presented as well as the final business plan (edited based on comments from the panel).
1. Presentation and ReviewRemember, presentation is important and you will want to make sure you all look your best. For the approximately 20-minute presentation, the following elements should be stressed:
2. Executive SummaryYou should also prepare to submit an executive summary for every panelist on the review board as well as the instructor(s)on the day of the presentation. This should summarize all the elements of your business plan.
3. Final Business PlanThe final business plan should be submitted the week after the presentation and should include:
IMPLEMENTATION, PRESENTATION, & CODE REVIEWThe final project will consist of those components detailed in the assignments as well as additional code, documentation, presentation and demonstration.
1. PresentationThe presentation should be tailored like a proposal to the committee for seeking capital for launching their business. The presentation should start with a brief overview of the business model and feasibility analysis. Discuss any changes in the anticipated projections from previous submission. The overview should focus on revenue projections based on the market analysis and expenditure plan. The rest of the presentation should show the functionality of the prototype and how the customers would interact with the business. The presentation should be very precise and focused rather than long and rambling! You should get to the point when dealing with investors and venture capitalists (their time is very limited). Please play your assigned roles in the team when you present, for instance, the CEO, the marketing director, technical director, chief financial officer, etc.
2. DemonstrationThe demonstration should show the functionality of your website service. You should show the servlets created (if not enough time allows- at least major servlets) as well as demonstrate how a new user would approach the site. Detail why everything was done and make it clear where something is "mocked" (using a static page) and not done using dynamic pages.
3. Application and DocumentationThe objectives of the application you are creating should include:
B +: A simple website using each of the technological criteria, with good quality code (2-3 servlets)
A -: A well-designed website with extensive reuse of code and wide use of appropriately designed components (> 5 servlets)
A: Excellent code, architecture and web site (should demonstrate ability better than other students in the class). Well-documented code. (> 5 servlets + JSPs)
Copyright © 2013, Sanjay Goel. All Rights Reserved.