Beruflich Dokumente
Kultur Dokumente
1. Virtual ClassroomInstructor-led web-based training http://www.cadence.com/support/virtual-classroom.aspx 2.Designing for the Virtual Interactive Classroom http://www.campus-technology.com/article.asp?id=11046 3. Postgre SQL: Manuals: SQL Commands: http://www.postgresql.org/docs/7.3/interactive/sqlcommands
2. THE OVERALL DESCRIPTION: Our approach is to build a system that would facilitate conducting seminars on Internet for participants from anywhere in world. Users can get many advantages by using virtual classroom. He can save a lot of time by using the virtual classroom to attend the session. 2.1 PRODUCT PROSPECTIVE The application is windows and Macintosh based. 2.1.1 HARDWARE INTERFACES 2.1.1.1 Screen resolutions of at least 800x600 required for proper and complete viewing of screens. Higher resolution would not be a problem 2.1.1.2 a working Internet connection is required for the working of the project 2.1.1.3 Intel Pentium processor 3 2.1.1.4 recommended 256 MB RAM 2.1.1.5 minimum hard disk of 40 GB 2.1.2 SOFTWARE INTERFACES Since the coding is done using JAVA, HTML & PHP languages so the compiler Dreamweaver, WAMP server is used which are compatible with a windows operating system. The MYSQL software is used for the database connectivity. 2.1.3 COMMUNICATION INTERAFCES The interface or the client mode is made using java and HTML languages and the server mode which connects the database and the client mode is made using PHP 2.2 PRODUCT FUNCTIONS Connects the student and teacher, promotes distant learning through Internet. 2.3 USER CHARECTERISTICS The user needs general computer knowledge to work on Internet. No expertise required. 2.4 CONSTRAINTS 2.4.1 HARDWARE LIMITATIONS: the compiler Dreamweaver is a 32 bit complier so it has compatibility issues with 64 bit systems 2.4.2 SOFTWARE LIMITATIONS: the program coding uses windows system file, it can work on Linux, Mac as well. Also works on windows 7 and windows vista. 3 SPECIFIC REQUIREMENTS: We require a working Internet connection for the working of this project.
3.1 SOFTWARE SYSTEM ATTRIBUTES: The product is reliable and easy to maintain. 3.1.1 PORTABLE can be used in all operating systems 3.1.2 SECURITY the knowledge shared is completely secured. No viruses can affect the project 3.1.3 REUSABLITY the information can be frequently reused 3.1.4 MAINTAINIBILTY its easily maintained however databases need to be upgraded regularly. Memory requirement is very small.
ER Diagram:
The physical data flow diagrams show the actual implements and movement of data between people, departments and workstations. A full description of a system actually consists of a set of data flow diagrams. Each component in a DFD is labeled with a descriptive name. The development of DFDS is done in several levels. Each process in lower level diagrams can be broken down into a more detailed DFD in the next level. The lop-level diagram is often called context diagram. It consists of a single process bit, which plays vital role in studying the current system. The process in the context level diagram is exploded into other process at the first level DFD.The idea behind the explosion of a process into more process is that understanding at one level of detail is exploded into greater detail at the next level. This is done until further explosion is necessary and an adequate amount of detail is described for analyst to understand the process. Larry Constantine first developed the DFD as a way of expressing system requirements in a graphical from, this lead to the modular design. A DFD is also known as a bubble Chart has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design. So it is the starting point of the design to the lowest level of detail. A DFD consists of a series of bubbles joined by data flows in the system.
0-Level DFD
1-Level DFD
3. UML
Unified Modeling Language (UML) is a standardized (ISO/IEC 19501:2005), generalpurpose modeling language in the field of software engineering. The Unified Modeling Language includes a set of graphic notation techniques to create visual models of objectoriented software-intensive systems. The Unified Modeling Language was developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software in the 1990s.[1] It was adopted by the Object Management Group (OMG) in 1997, and has been managed by this organization ever since. In 2000 the Unified Modeling Language was accepted by the International Organization for Standardization (ISO) as industry standard for modeling software-intensive systems. The current version of the UML is 2.4.1 published by the OMG in August 2011.
4. Activity Diagram:
5. Interaction Diagrams:
Sequence Diagrams: