Dissertation Submitted
In Partial Fulfillment ofInformatics
Practice Curriculum
KENDRIYA VIDYALAYA
KAILASHAHAR
Guidance: B.L .kashyap, PGT (COMPUTER SCIENCE)
PREPARED BY: Master Suman Dey
Master Jagannath Debbarm
Master Oiman Thoiba Singha
SCHOOL CODE:-
This is to certify that Master Suman Dey Master Jagannath Debbarma & Master OinamThoiba Singhawho are students of Informatics Practices(code;065)have successfully completed the project work in the partial fulfillment of theInformatics practices.
MR B.L Kashyap
PGT (Computer Science)
K.V ALWAR (N) Tripura
Declaration by the candidate
We declare that the project report “shopping management” is a benefited record of the project work, carried out by us at anywhere. This project is developed by us during the academic period w.e.f 1th November 2010 to 15th December2010. It has not been submitted for any other examination or competition. This is developed in partial requirement for the award for theAISSCE.
GUIDED BY MR B. L. KASHAYP
NAME- Suman dey(PCM)
Class- xii, roll-no:
name– Jagannath Deb Barma(PCB)
CLASS- XII,ROLL-NO:
Name- oinam thoiba singha(pcb)
Class- XII, ROLL-NO:
We express our humble gratitude to our IP teacher who has been the source of the inspiration to us in taking up this project. We also thank our Principal sir Sri D. Patle for this active concerned information and effort in making it successful.
I would like to thank our computer expert MR B. Chakma for his kind co-operation.
I hope that the project in the present form would prove in the expectation of the teacher concerned in spite of some inadequacies.
HARDWARE AND SOFTWARE
HARDWARE Specification of machine used:
Processor : Intel
Memory[RAM] : 16 MB
Hard Disk Drive : 1.5 GB
Display Type : Digital monitor
Keyboard : Multimedia
Control : ASCII
Printer : Ink Jet
CD ROM DRIVE:
48x or 52x higher (to installation)
Software (o.s, languages, packages).
Operating System:
Windows XP or Higher Version.
Languages:
Java (front end) & My Sql (Back end).
REQUIREMENTS ANALYSIS:-
Software architecture design
1. Introduction of sad
2. Entity Relationship diagram (ERD)
3. Interfaces.
4. Databases.
PREFERENCES :
- THE COMPLETE REFERENCE BY HERBERT SCHILDT
- GRAPHIC JAVA MASTERING THE JFC BY GEARY DAVID M
- MYSQL DATABASE BY LERRY ULMAN
Objective and scope of the project:
The objective of the proposed system would be to overcome the problems faced in the manual system. Updating records would not be a problem and also cross checking of a records in the proposed system would not be required.
Mathematical, accounting and logical errors would get automatically rectified in the proposed system. Report can be generated on the click of a button. Design of the proposed system must take the following into the consideration. The Shopping management and maintenance application for a shop should have all the data pertaining to the employees working in the shop. The system should have records of the entire customer who visit the shop. The system should record the data of all the shopmaterials, availability and the company that manufacture these materials.
This, system play’s a vital role in having a systematic and easy to work with area. In that project the entire thing are first, given a unique number that must not be duplicated and then they are arranged in a proper sequenced order. So that it becomes easy to keep track all the things and information about them.
It is manually a very different job to perform and it needs a lot of recalling, reminding and calculation, which exhausts the mind of the humanware, where the entire problem is solved by the computerization of shopping complex. This computerization of the shop helps to owner & employees to keep information & details of customers,dealers etc. in quick & short time.
Algorithm :-
We can define on algorithm as an ordered sequence of well-defined calculation, that when executed will always produce a result and terminates in a finite amount of time.
FEATURE OF ALGORITHMS:-
An algorithm must always clearly understand starting and ending point.
Each individual operation must be well defined.
In developing an algorithm there will not be any rules.
After algorithm terminates the design result must be obtained.
A process model of a hierarchy of level DFD’S.
The DFD’S in the process model highlight the functions of the system. The interaction amongst the function is modledd using the data flow and the data stores for the completeness of the process model one need to give the detailed specification of the elementary or structured. An elementary data item is one, which cannot be decomposed into smaller component. An elementary data item is also called a data element. A structure data item is made up of components. The components of data structure can they be structure data elementary item. A structure data item is also called data structure. Data flows and data store describing data structure.
Introduction
@@ Data flow diagram is a graphical technique that depicts information flow and the transforms that are applied as data move from input to output.
@@ DFD is also known as Data Flow Graph or a bubble Graph.
LEVELS OF DFD
## Data are partitioned into different levels that represent increasing information flow and functional detail. So, DFD provides mechanisms for functional modelling as well as information flow modelling.
## Data flow diagram can be drawn up to “n” numbers of level. Each text level uncovers the abstraction of system.
The following aspects of his system can be molded using a data flow diagram.
What function must be system performing?
What the interaction is between carried out by this function?
What input are transformed?
Form where does the system receive the inputs?
Hence the statement in structure flow chart can be put together in the following three ways only.
- Sequence.
- Selection.
- Iterative.
A non-procedure process specification defined was the process earns estimation being density the recess.
Now a day the software peoples are in a lot of concern for their advancement and knowledge of their technical skills. Our goal is to create a product that helps to manage collection of things of any complex. This software provides the all basic functionality with quick, accurate with 100% reliability. By using this software a company can handle their complex.
$$ Requirements analysis is a software engineering task that bridges the gap between system level software allocation and software design. Following figure shows importance of requirement analysis.
$$ It specifies software function and performance, indicate software interface with other system elements, and establish design constrains that the software must meet.
$$ It allows software engineer to refine the software allocation and build models of the process, data and behavior domains that will be treated by software.
$$ It provides the software designer with a representation of information and function that can be translated to data, architecture and procedural design.
Software architecture eludes “the overall structure of the software and the wasp in which that structure provides conceptual integrity for a system” in its simplest form architecture is the hierarchical of program components (modules) the manager in which these components interact, and the structure of the data that are used by the components.
Our goal of software design to derive an architecture rendering of a system. This rendering service a framework for which more detailed design activities are conducted. A set of architecture pattern enables a software engg. To reuse design-level concept.
Structural Properties.
This aspect of the architecture design representation defines the components of a system (e.g., modules, objects) and the manner in which those components are packed to encapsulate both data, and to interact of methods.
Extra functionality properties
The architecture design description should address how the design architecture achieves requirements for performance, capacity, reliability, security, adaptability and other system characteristics.
Families of Related System
The architecture design description should draw upon repeatable patterns that are commonly encountered in the design of families of similar system. In essence, the design should have the ability to reuse architecture building blocks.
Structural models represent architecture as an organized collection of program components.
Framework models increase the level of design abstraction by attempting
To identify repeatable architecture design frameworks (patterns) those are encountered in similar types of applications.
Dynamic models address the behavior aspects behavioral aspects of the program architecture, indicating how the structure configuration may as a function of external events.
Process models focus on the design aspects of the business or technical process that the system must acceptable.
Finally we have the functionality model which can be used to represent the functionality of a system.....
ENTITY RELATIONSHIP:
DIAGRAM
The entire relationship data model is based on a perception of a real world that consists of a set of basic objects called entities, and of relationships among these objects. It was developed to facility database design by allowing the specifications of an enterprise schema, which represents the overall logical structure of a database. The E-R data model is one of several semantic data models: the semantic aspects of the model lies in the attempt to represent the meaning of the data. The E-R model is extremely useful in mapping the meaning and interactions of real world enter prices onto a conceptual scheme. Because of this utility, many databases design tools drawn on concepts from the E-R model.
The entity is a “thing” or “object” in the real world that is distinguishable from all other objects. For example, each person who is an enterprise is an entity. An entity has a set of properties, and the values for some set of properties, and the values for some set of properties may uniquely indentify an entity.
Thus, an entity set of entities of the same type that share the same properties, or attributes. For example, the set of all properties my uniquely indentify an entity.
ATTRIBUTE :
The entity is represented by a set of attributes. Attributes are descriptive properties possessed by each member of an entity set. As example attributes of the customer entity set are customer name, social properties, Customer Street, customer city, etc.
Attributes can be simple and composite, single and multi valued, null and derived.
RELATIONSHIP SET :
A relationship is an association among several entities. A relationship set a set of relationships of the same type. Formally, it is a mathematically relation on
n>=2 entity set €1€2...... €n are entity sets, then a relationship sets, then a relationship set R is a subset of
{ (€1€2...... €n} €1 ἕ €1 ,€2 ἕ €2,...... €n ἕ €n}
Where (€1 €2 ,...... €n )
MAPPING CARDINATITY:
We have defined a set of objects and represented the object relationships pairs that bind them. But the simple pair that states: Object xrelates to objectD does not provide enough information. We must understand how many occurrences’ of objectsx are related to how many occurrences’ of objects D.This leads to s data modelling concepts called Cardinality.
Cardinality is the specification of the number of occurrence of one [object] that can be related to the number of occurrences of another t[object]. It is usually expressed as simply “one” or “many”.
The mapping cardinality must be one of the following:
@@ One to one: An entity A is associated with at most one entity in B, and. And an entity B is associated with at most one entity in A.
@@ One too Many: An entity A is associated with any number of entities in B, and. And an entity B is however, can be associated with at most one entity in A.
@@ Many to one: An entity A is associated with at most one entity in B, and. And an entity B however, can be associated with any number of entities in A.
@@Many too many: An entity A is associated with any most one entity in B, and. And an entity B is associated with any number of entities in A.
The appropriate mapping Cardinality for a particular relationship set is obviously dependent on the real-world situation that is being modeled by the relationship set.
ENTIRE RELATIONHIP DIAGRAM COMPONENTS
TheE-Rdiagram can be expressing the overall logical structure of databases graphically. Such a diagram consists of the following major components:
## Rectangle: - Represents entity sets
## Ellipse: - Represents attributes
## Diamonds: -Represents relationship sets
## Lines: - which links attributes to entity sets and entity sets and entity sets to relationship sets
## Double Ellipse: - Represents multi valued attributes.
## Dashed Ellipse: - Denotes derived attributes
## Double Line: - Indicates total participation of an entity in a Relationships set.