Presentation on theme: "Daniel Harrington Chris Fleenor Brian Bogovich Andrew Miles."— Presentation transcript:
Daniel Harrington Chris Fleenor Brian Bogovich Andrew Miles
The System Client: Susan Wiediger, SIUE Chemistry Department Goal: Create a system to facilitate the creation and use of a pattern language.
What is a Pattern Language? Pattern – A pattern is an empirically tested solution to a recurring problem.
Example Pattern Name: Translating Multiple Representations Author: SDW Dates: Written December 2003; Last revised 1 December 2003 Context: Contributes to larger scale patterns “Introducing New Topic,” “Lecture Design,” “Lab/Lecture Coordination,” and “Language Acquisition” Headline: Chemists use multiple descriptions of the same process to emphasize particular aspects of the process, to make certain manipulations clearer and easier, and for typographical convenience. Learning to understand all these representations and translate between them is a crucial skill on the road to expertise that is difficult to acquire.
Example Pattern Abstract: Chemists use many levels of descriptions, from macroscopic observations to microscopic interpretations and representations of both levels in symbols and words. Different representations reveal different aspects of the process, and so learning to understand all the different representations is critical to the novice’s development in chemistry. To aid in this process, it is important to not only show the connections between the different representations, but to do so explicitly and repeatedly, and then require the student to practice with the representations. This is analogous to other types of language acquisition, with the added level of pictorial representations.
Example Pattern Body:This pattern manifests over and over at all levels of chemistry, as in many subjects. Similar to learning the “jargon” or “terms of art” in a particular field, the novice has languages as well as content to learn in any new area. The particular area of language acquisition dealt with in this pattern is more than learning new words in a familiar language, such as what concrete objects are referred to by terms like chlorine, sodium, buret, or even to learning a new meaning for a familiar word, such as balance or reduce. Instead this pattern focuses on the layers of different representations used for the same substance. Often these layers are described by the terms macroscopic, microscopic, and symbolic, but even within a particular category (especially symbolic) a given substance or process may have multiple representations…..
Example Pattern Solution: Show multiple representations in parallel, explaining why there are different representations and how they are similar and/or different. Use all types of representations to provide cross- references. In a classroom setting, give homework and lab assignments that require students to create, interpret, and translate the different views.
Example Pattern Examples:Currently, this section shows examples of the multiple representations that are appropriate for some different subjects, rather than explicit scripts for how one might use the different views in the course of a lecture or discussion. Pictures are from McMurry and Fay “Chemistry” 2nd Edition, Prentice-Hall, and are for illustration purposes only Common name: table salt Technical name: sodium chloride Symbolic formula: NaCl Macroscopic View Microscopic View
Example Pattern Subsystems: Implementation may require “Effective Multimedia,” “Structure, Guide, Fade,” “Homework Sets,” “Effective Demonstrations”
Pattern Language Pattern Language - A pattern language is a hierarchical structure of linked patterns that can be navigated to select the subset of patterns appropriate to a particular situation.
Example Pattern Graph Introducing new topic Lecture Design Lab/Lecture Coordination Language Acquisition Effective Multimedia Effective Demonstrations Structure, Guide, Fade Homework Sets ? Context: Subpatterns:
Functional Requirements Administrators Create, edit, and remove patterns. Other Users Browse patterns by list, searching, and hierarchy Save a subset of the pattern language Post feedback about patterns
Other Requirements Nonfunctional Web based interface User accounts Security Pseudo Microsoft Access Database
Design Goals Security: The administrator’s privileges must not be accessible to other users. Administrators have potentially damaging privileges. Availability: The system will be available to anyone with access to the internet. Development Cost – The client does not expect to pay any money for the delivery of the system. Readability – The code of the system will be a deliverable, and the client to have other people maintain the project. The readability of the code is important.
Training Plan Internal Training –Team members train themselves as necessary Languages –ASP.NET –C# Operating Systems –IIS component of Windows 2000/XP Interfacing with Other Subsystems –Interface between ASP and MS Access
Training Plan External Training –Installation Initial installation done by team Instructions for configuring IIS, backups of all web pages, and instructions for setting up database included in case re- install is needed –Using the System User’s Manual provided –Maintenance Client intends for Prof. Kalinowski to handle system maintenance and modification; no training needed
Process Plan Lifecycle model –Waterfall with SubProjects Why? –Risks and requirements are well defined from the beginning –Project can easily be broken into subprojects
Testing Plan Module Testing Access Database Microsoft Access User Interface Explorer Stub Data Communication Preliminary Database Simple UI
Testing Plan Integration Testing Access Database No stub or driver User Interface No stub or driver Data Communication User Interface Driver
Testing Plan System Testing –Set up servers with our system –Add many patterns to the database Acceptance Testing
Installation and Operation System Requirements –Server Web-accessible server capable of running MS Access Database –Client Up-to-date web browser Migration –No current system from which to migrate Introduction of Data –Initial data will be provided by client –Client and administrators responsible for validation of data
Risk Management Risk DescriptionProbabilityDelay CausedRisk ExposureProbable Solution Loss of team member10%4 weeks0.4 weekWork divided among remaining members Personnel problems10%1 week0.1 weekConflict resolution within group or with upper management Training in ASP.net and C# takes too long 10%1 week0.5 weekAlternate implementation User formatted input does not work as expected 30%1 week0.3 weekTeam will have to find a new way to do formatted text input estimated overrun: 1.3 weeks
Your consent to our cookies if you continue to use this website.