MAPING :
Minggu, 03 Mei 2009
Sabtu, 25 April 2009
Normalization
The cosine measure normalizes document length so that long
documents are not favored simply because they have more terms.
Later work empirically showed that, for the TREC collection,
longer documents actually have a higher probability of being
relevant [1]. We show that the slope should be recalibrated for fundamentally
different document collections. We recomputed the normalization
for the web track and obtained a 16% improvement in our
baseline run. The resulting effectiveness from this sole
modification was an average precision higher than any other
group who submitted results to the TREC-10 web track.
Design Database Process (review)
The process includes:
· Gathering user or business's requirement
· Develop E-R Model bases user or business's requirements
· Convert E-R Model go to relationship gatherings (table)
· Relationship normalization to remove anomaly
· Implementation goes to database by make table for each relationship already most normalization
Database normalization
* Normalization is the establishment of the database structure process so that most of the ambiguity can be removed.
* Normalization stage, starting from the most mild (1NF) to most stringent (5NF)
* Usually only up to the level of 3NF or BCNF because already sufficient to generate the table-a table of good quality.
* Why do normalization?
Ø Optimizing table structures
Ø Increase speed
Ø To remove income of same data.
Ø More efficient in the use of storage media
Ø Reduce redundancy
Ø Avoid anomalies (insertion anomalies, deletion anomalies, update anomalies).
Ø Improved data integrity
* A table saying good (efficient) or if the normal 3 to meet the following criteria :
Ø If there is decomposition (decomposition) table, it must be guaranteed safe decomposition it (Lossless-Join Decomposition). That is, after the table is described / decompositioned a new table-table, the table-table can generate a new table with the same exact.
Ø Maintain dependence on the functional changes in data (Dependency preservation).
Ø Does not violate Boyce-Code Normal Form (BCNF)
* If the third criteria (BCNF) can not be met, then at least the table does not violate the Normal Form of the third stage (3rd Normal Form / 3NF).
Information Systems Analysis and Design [Part-6]
Posting by my name is onix on 2:01 AM
DATABASE NORMALIZATION
Design Database Process (review)
The process includes:
· Gathering user or business's requirement
· Develop E-R Model bases user or business's requirements
· Convert E-R Model go to relationship gatherings (table)
· Relationship normalization to remove anomaly
· Implementation goes to database by make table for each relationship already most normalization
Database Normalization
Normalization is process of database structure forming so mainly part of ambiguity can be removed. Normalization phase is begun from lightest phase (1NF) until tightest (5NF). Usually, only coming up with level 3NF or BCNF because has adequate enough to yield the tables of which with quality goodness.
Why done by normalization?
• Optimizing table structures
• Increasing speed
• Removing same data inclusion
• More efficient in storage media purpose
• Reducing redundancy
• Avoiding anomaly (insertion anomalies, deletion anomalies, and anomaly's update).
• Increased data integrity
One table is said well (efficient) or normal if accomplish 3 criterions as follows:
- If there is decomposition (parsing) table, therefore the decomposition shall be secured safe (Lossless Join Decomposition). It’s mean, after that table is untied / at decomposition becomes new tables, that new tables can result original table equally exactly
- Its preserve dependency functional at the moment data change (Dependency Preservation).
- Don't breach Boyce-Code Normal Form (BCNF)
If the third criterion (BCNF) can't be accomplished, therefore at least that table not breach the third Normal Form (3rd Normal Form/ 3NF).
Functional Dependency
Functional Dependency figuring relationship attributes in one relationship. An attribute is said functionally dependant on the other if we utilize the attributes value to determine the other attribute value. Symbol that is utilized is for representing functional dependency.
Read functionally determines.
Notation: A B
A and B is attribute of one table. It means that functionally A determines B or B depend on A, if and only if available 2 rows data with same value of A, therefore value of B also same.
Notation:
Functional Dependency:
* NRP -> Name
* Study_lecture, NRP -> grade/value
Non Functional Dependency:
* Study_lecture -> NRP
* NRP -> grade/value
* Functional Dependency from the value table :
Ø NRP -> Name
Because for each value Nrp the same, then the value of the same name.
Ø {Study_lecture, NRP } -> grade/value
Because the value of attributes depending on the NRP and Study_lecture together. In another sense Study_lecture for the NRP and the same, they also rated the same, because Study_lecture and the NRP is a key (is unique).
Ø Study_lecture ->/ NRP
Ø NRP ->/ value
First Normal Form - 1NF
A table on the form said to be normal if I did not reside in the unnormalized form of a table, where there is a kind of field multiplication and field that allows a null (empty).
not be allowed :
* Attributes which many valuable (Multivalued attributes).
* Attributes composite or a combination of both.
So that :
* Price of the attribute domain must be atomic rates.
v Example Student Data as follows:
The tables above are ineligible for 1NF. Decomposition becomes:
Collegian table:
Hobby table:
Second Normal Form - 2NF
* Normal form 2NF met in a table if it meets the form of 1NF, and all the attributes than the primary key, have a full Functional Dependency on primary key
* A table does not meet 2NF, if there are attributes that dependence it (Functional Dependency) are only partial (only depending on the part of the primary key)
* If there are attributes that have no dependence on the primary key, then the attributes must be moved or removed
* Functional dependence X -> Y , said full if it is said to delete an attribute A from X means that Y is no longer dependent functional.
* Functional dependence X -> Y , said partial if a delete attribute A from X means that Y is functionally dependent.
* Relation scheme R in the form 2NF if every non-primary key attribute A Î R depend on the full functional primary key R.
* For example :
Ø The following table meet 1NF, but not including 2NF
Ø Does not meet 2NF, because (NIM, CodeMk) is regarded as the primary key whereas:
{NIM, CodeMk} à NameMhs
{NIM, CodeMk} à Address
{NIM, CodeMk} à LectureStudy
{NIM, CodeMk} à Sks
{NIM, CodeMk} à LetterValue
Ø The table needs to decomposition to become some table eligible 2NF.
Ø Functional dependency it as follows:
o {NIM, CodeMk} à LetterValue (fd1)
o NIM à {NameMhs, Address} (fd2)
o CodeMk à {LectureStudy, Sks} (fd3)
Ø So that :
o fd1 (NIM, CodeMk, LetterValue) à Table of Value
o fd2 (NIM, NameMhs, Address) à Table of Student
o fd3 (CodeMk, LectureStudy, Sks) à Table of LectureStudy
Third Normal Form - 3NF
* Normal form 3NF fulfilled if the form meets 2NF, and if there are no non-primary key attribute that has a dependence on non-primary key attributes of the other (transitive dependencies).
* For example :
Ø This following table of students eligible 2NF, but does not meet to 3NF :
Ø Because there are non-primary key attribute (ie, City and Provincial), which has a dependence on non-primary key attributes of the other (ie PostCode):
PostCode à {City, Province}
Ø So that the table need to decomposition to becomes
Ø Student (NIM, NameMhs, Street, PostCode)
o PostCode (PostCode, Province, City)
Boyce-Codd Normal Form (BNCF)
* Boyce-Codd Normal Form constraint has a stronger form of the third Normal. To be BNCF, relations must be in the form of first Normal and forced each of the attributes depends on the function in the super key attributes.
* In the example below there is a relationship seminar, Primary Key is NPM + Seminar.
Students may take one or two seminars. Each seminar requires 2 each of the students and led by one of the 2 seminar. Each leader can only take one seminar course. NPM in this example and the Seminar show a Preceptor.
Seminar Relationship
Seminar Relationship form is third Normal Form, but not BCNF since Seminar Code is still dependent function on Counselor, if each Counselor gets to teach just one seminar. Dependent seminar on one attribute is not super key as presupposed by BCNF. Therefore Seminar relationship shall be broken down as two which is:
Seminar - Preceptor Relationship
Fourth and fifth Normal Form
Relationship in fourth normal form (4 NF) if relationship in BCNF and not contains of multi value dependency. To remove multi value dependency from one relationship, we are divide relationship become two new relationships. Each relationship contains of two attributes that have multi value relationship.
Relationship in fifth normal form (5NF) get business with property is called join without marks sense information loss (lossless join). The fifth normal Form (5 NF also called PJNF (projection join normal form). This case is very rare to appearance and hard to be detected practically
References:
1. Agus Sanjaya ER,S.Kom, M.Kom, slide presentation : Database and ER-Diagram
2. Network Intrusion Detection: Evasion,
Traffic Normalization, and End-to-End Protocol Semantics
documents are not favored simply because they have more terms.
Later work empirically showed that, for the TREC collection,
longer documents actually have a higher probability of being
relevant [1]. We show that the slope should be recalibrated for fundamentally
different document collections. We recomputed the normalization
for the web track and obtained a 16% improvement in our
baseline run. The resulting effectiveness from this sole
modification was an average precision higher than any other
group who submitted results to the TREC-10 web track.
Design Database Process (review)
The process includes:
· Gathering user or business's requirement
· Develop E-R Model bases user or business's requirements
· Convert E-R Model go to relationship gatherings (table)
· Relationship normalization to remove anomaly
· Implementation goes to database by make table for each relationship already most normalization
Database normalization
* Normalization is the establishment of the database structure process so that most of the ambiguity can be removed.
* Normalization stage, starting from the most mild (1NF) to most stringent (5NF)
* Usually only up to the level of 3NF or BCNF because already sufficient to generate the table-a table of good quality.
* Why do normalization?
Ø Optimizing table structures
Ø Increase speed
Ø To remove income of same data.
Ø More efficient in the use of storage media
Ø Reduce redundancy
Ø Avoid anomalies (insertion anomalies, deletion anomalies, update anomalies).
Ø Improved data integrity
* A table saying good (efficient) or if the normal 3 to meet the following criteria :
Ø If there is decomposition (decomposition) table, it must be guaranteed safe decomposition it (Lossless-Join Decomposition). That is, after the table is described / decompositioned a new table-table, the table-table can generate a new table with the same exact.
Ø Maintain dependence on the functional changes in data (Dependency preservation).
Ø Does not violate Boyce-Code Normal Form (BCNF)
* If the third criteria (BCNF) can not be met, then at least the table does not violate the Normal Form of the third stage (3rd Normal Form / 3NF).
Information Systems Analysis and Design [Part-6]
Posting by my name is onix on 2:01 AM
DATABASE NORMALIZATION
Design Database Process (review)
The process includes:
· Gathering user or business's requirement
· Develop E-R Model bases user or business's requirements
· Convert E-R Model go to relationship gatherings (table)
· Relationship normalization to remove anomaly
· Implementation goes to database by make table for each relationship already most normalization
Database Normalization
Normalization is process of database structure forming so mainly part of ambiguity can be removed. Normalization phase is begun from lightest phase (1NF) until tightest (5NF). Usually, only coming up with level 3NF or BCNF because has adequate enough to yield the tables of which with quality goodness.
Why done by normalization?
• Optimizing table structures
• Increasing speed
• Removing same data inclusion
• More efficient in storage media purpose
• Reducing redundancy
• Avoiding anomaly (insertion anomalies, deletion anomalies, and anomaly's update).
• Increased data integrity
One table is said well (efficient) or normal if accomplish 3 criterions as follows:
- If there is decomposition (parsing) table, therefore the decomposition shall be secured safe (Lossless Join Decomposition). It’s mean, after that table is untied / at decomposition becomes new tables, that new tables can result original table equally exactly
- Its preserve dependency functional at the moment data change (Dependency Preservation).
- Don't breach Boyce-Code Normal Form (BCNF)
If the third criterion (BCNF) can't be accomplished, therefore at least that table not breach the third Normal Form (3rd Normal Form/ 3NF).
Functional Dependency
Functional Dependency figuring relationship attributes in one relationship. An attribute is said functionally dependant on the other if we utilize the attributes value to determine the other attribute value. Symbol that is utilized is for representing functional dependency.
Read functionally determines.
Notation: A B
A and B is attribute of one table. It means that functionally A determines B or B depend on A, if and only if available 2 rows data with same value of A, therefore value of B also same.
Notation:
Functional Dependency:
* NRP -> Name
* Study_lecture, NRP -> grade/value
Non Functional Dependency:
* Study_lecture -> NRP
* NRP -> grade/value
* Functional Dependency from the value table :
Ø NRP -> Name
Because for each value Nrp the same, then the value of the same name.
Ø {Study_lecture, NRP } -> grade/value
Because the value of attributes depending on the NRP and Study_lecture together. In another sense Study_lecture for the NRP and the same, they also rated the same, because Study_lecture and the NRP is a key (is unique).
Ø Study_lecture ->/ NRP
Ø NRP ->/ value
First Normal Form - 1NF
A table on the form said to be normal if I did not reside in the unnormalized form of a table, where there is a kind of field multiplication and field that allows a null (empty).
not be allowed :
* Attributes which many valuable (Multivalued attributes).
* Attributes composite or a combination of both.
So that :
* Price of the attribute domain must be atomic rates.
v Example Student Data as follows:
The tables above are ineligible for 1NF. Decomposition becomes:
Collegian table:
Hobby table:
Second Normal Form - 2NF
* Normal form 2NF met in a table if it meets the form of 1NF, and all the attributes than the primary key, have a full Functional Dependency on primary key
* A table does not meet 2NF, if there are attributes that dependence it (Functional Dependency) are only partial (only depending on the part of the primary key)
* If there are attributes that have no dependence on the primary key, then the attributes must be moved or removed
* Functional dependence X -> Y , said full if it is said to delete an attribute A from X means that Y is no longer dependent functional.
* Functional dependence X -> Y , said partial if a delete attribute A from X means that Y is functionally dependent.
* Relation scheme R in the form 2NF if every non-primary key attribute A Î R depend on the full functional primary key R.
* For example :
Ø The following table meet 1NF, but not including 2NF
Ø Does not meet 2NF, because (NIM, CodeMk) is regarded as the primary key whereas:
{NIM, CodeMk} à NameMhs
{NIM, CodeMk} à Address
{NIM, CodeMk} à LectureStudy
{NIM, CodeMk} à Sks
{NIM, CodeMk} à LetterValue
Ø The table needs to decomposition to become some table eligible 2NF.
Ø Functional dependency it as follows:
o {NIM, CodeMk} à LetterValue (fd1)
o NIM à {NameMhs, Address} (fd2)
o CodeMk à {LectureStudy, Sks} (fd3)
Ø So that :
o fd1 (NIM, CodeMk, LetterValue) à Table of Value
o fd2 (NIM, NameMhs, Address) à Table of Student
o fd3 (CodeMk, LectureStudy, Sks) à Table of LectureStudy
Third Normal Form - 3NF
* Normal form 3NF fulfilled if the form meets 2NF, and if there are no non-primary key attribute that has a dependence on non-primary key attributes of the other (transitive dependencies).
* For example :
Ø This following table of students eligible 2NF, but does not meet to 3NF :
Ø Because there are non-primary key attribute (ie, City and Provincial), which has a dependence on non-primary key attributes of the other (ie PostCode):
PostCode à {City, Province}
Ø So that the table need to decomposition to becomes
Ø Student (NIM, NameMhs, Street, PostCode)
o PostCode (PostCode, Province, City)
Boyce-Codd Normal Form (BNCF)
* Boyce-Codd Normal Form constraint has a stronger form of the third Normal. To be BNCF, relations must be in the form of first Normal and forced each of the attributes depends on the function in the super key attributes.
* In the example below there is a relationship seminar, Primary Key is NPM + Seminar.
Students may take one or two seminars. Each seminar requires 2 each of the students and led by one of the 2 seminar. Each leader can only take one seminar course. NPM in this example and the Seminar show a Preceptor.
Seminar Relationship
Seminar Relationship form is third Normal Form, but not BCNF since Seminar Code is still dependent function on Counselor, if each Counselor gets to teach just one seminar. Dependent seminar on one attribute is not super key as presupposed by BCNF. Therefore Seminar relationship shall be broken down as two which is:
Seminar - Preceptor Relationship
Fourth and fifth Normal Form
Relationship in fourth normal form (4 NF) if relationship in BCNF and not contains of multi value dependency. To remove multi value dependency from one relationship, we are divide relationship become two new relationships. Each relationship contains of two attributes that have multi value relationship.
Relationship in fifth normal form (5NF) get business with property is called join without marks sense information loss (lossless join). The fifth normal Form (5 NF also called PJNF (projection join normal form). This case is very rare to appearance and hard to be detected practically
References:
1. Agus Sanjaya ER,S.Kom, M.Kom, slide presentation : Database and ER-Diagram
2. Network Intrusion Detection: Evasion,
Traffic Normalization, and End-to-End Protocol Semantics
Minggu, 19 April 2009
DATABASE AND ER-DIAGRAM
Data Base Definition
data base of vital importance for one who know computer more, especially for a programmer. because database can also be called with the heart of from system at make by a programmer or one who make system
data base definition as follows:
• stored data nest in magnetic disk, optical disk or another secondary storage inwrought
• collection from data mutual related from a enterprise (companies, government resort or private)
1. manufacturing business à production planning data, recent production data, materials order data, etc
2. hospital? patient data, doctor, nurse, etc
database management system :
• database collection/federation with application software based on database
• these application program is used to accessing and take care database
• principal aim dbms prepares a easy environment and efficient for use, withdrawal and data storage and information
beet, byte, field :
• beet -> be smallest data part value containing 0 or 1
• byte -> collection from beets of a kind
• field -> nest byte of a kind, in data base is used attribute term
attribute/field :
• be character or characteristics from a entity that prepare to prepare detail explanation about entity
• a also can has attribute
• attribute example:
1. student university: nim, name, address
2. car: nomor_plat, colour, kind, cc
attribute types :
• single vs multivalue :
1. single -> only can loaded at most one value
2. multivalue? can loaded with interest from one value with same type
• atomic vs composition :
1. atomic à indiscrete into attribute smaller
2. composition? be federation from several attributes smaller
• derived attribute
1. attribute the value can be produced from attribute value other, example à age that produced from date attribute born
• null value attribute
1. attribute doesn't has value to a record
• mandatory value attribute
2. attribute that must has value
record/tuple :
• be a data line in a customer
• consist of where is attributes mutual connected to information entity/customer in its entirety
entity/file:
• file is collection from record of a kind and has element same, attribute same but vary data value.
• file type
in application processing, file can category as follows:
1. mother file
2. transaction file
3. report file
4. history file
5. patron file
6. work file
Domain :
• domain be collection from values that permitted to stay in one or more attribute. every attribute in a data base relation defined as a(n) domain
data element key :
• key element record that worn to find record when does access or can also be used to identify every entity/record/line.
kinds key :
• superkey be one or more attribute from a table that can be used to identify entityty/record from table uniquely (not all attributes be superkey)
• cadidate key super key with minimal attribute. candidate key can not full attribute from other table so that candidate key beyond question superkey but not yet sure on the contrary.
• primary key
• one of [the] attribute from candidate key can be choose/determined to be primary key with three criteria as follows:
1. key more natural to be used as reference
2. key simpler
3. key well guarantee the uniqueness
• alternate key attribute from candidate key not chosen be primary key.
• foreign key be just any attribute that indicate to primary key in other table. foreign key will happen at one particular customer that has kardinalitas one to many (one to many) or many to many (many to many). foreign key usually always put in table that aim to many.
• external key be a lexical attribute (or collection lexical attribute) the values always identify one object instance.
ERD (entity relationship diagram):
• ERD a network model that use wording that kept in system according to abstract.
• difference between DFD and ERD :
1. DFD will be a function network model that be carried out by system
2. ERD be data network model that emphasized in structure and relationship data
elements ERD :
• entity -> in ER diagram entity described with long square form. entity something that there in real system also where does stored data or where found data.
• relationship ->in ER diagram relationship can be described with a lozenged. relationship natural connection that between entity. in general given name with verb base so that make easy to do the customer reading.
• relationship degree -> total entity that participate in one relationship. degree often worn in ERD.
• attribute ->character or characteristics from every entity also relationship
• kardinalitas -> show optimum tupel that can relation with entity in entity other
degree relationship
• unary relationship -> model relationship that between entity that come from entity set same.
• binary relationship ->model relationship that between 2 entity.
• ternary relationship -> be relationship between instance from 3 types entity unilaterally.
Kardinalitas :
• found 3 kardinalitas customer that is :
1. one to one: connection level one to one declared with one incident in entity first, has only one connection with one incident in entity second and on the contrary.
2. one to many or many to one: connection level one to many equal to many to one depending from which direction connection seen. to one incident in entity first can has many connection with incident in entity second, if on the contrary one incident in entity second only can has relation with one incident in entity first.
3. many to many: happen if every incident in a entity has many connection with incident in entity another.
example kardinalitas :
notation (diagram e-r) :
• symbolic notation in diagram ER
1. long square declares collection entity
2. circle declares attribute
3. slit ketupat declare customer collection
4. line as liaison between customer collection with collection entity and collection entity with the attribute
data base of vital importance for one who know computer more, especially for a programmer. because database can also be called with the heart of from system at make by a programmer or one who make system
data base definition as follows:
• stored data nest in magnetic disk, optical disk or another secondary storage inwrought
• collection from data mutual related from a enterprise (companies, government resort or private)
1. manufacturing business à production planning data, recent production data, materials order data, etc
2. hospital? patient data, doctor, nurse, etc
database management system :
• database collection/federation with application software based on database
• these application program is used to accessing and take care database
• principal aim dbms prepares a easy environment and efficient for use, withdrawal and data storage and information
beet, byte, field :
• beet -> be smallest data part value containing 0 or 1
• byte -> collection from beets of a kind
• field -> nest byte of a kind, in data base is used attribute term
attribute/field :
• be character or characteristics from a entity that prepare to prepare detail explanation about entity
• a also can has attribute
• attribute example:
1. student university: nim, name, address
2. car: nomor_plat, colour, kind, cc
attribute types :
• single vs multivalue :
1. single -> only can loaded at most one value
2. multivalue? can loaded with interest from one value with same type
• atomic vs composition :
1. atomic à indiscrete into attribute smaller
2. composition? be federation from several attributes smaller
• derived attribute
1. attribute the value can be produced from attribute value other, example à age that produced from date attribute born
• null value attribute
1. attribute doesn't has value to a record
• mandatory value attribute
2. attribute that must has value
record/tuple :
• be a data line in a customer
• consist of where is attributes mutual connected to information entity/customer in its entirety
entity/file:
• file is collection from record of a kind and has element same, attribute same but vary data value.
• file type
in application processing, file can category as follows:
1. mother file
2. transaction file
3. report file
4. history file
5. patron file
6. work file
Domain :
• domain be collection from values that permitted to stay in one or more attribute. every attribute in a data base relation defined as a(n) domain
data element key :
• key element record that worn to find record when does access or can also be used to identify every entity/record/line.
kinds key :
• superkey be one or more attribute from a table that can be used to identify entityty/record from table uniquely (not all attributes be superkey)
• cadidate key super key with minimal attribute. candidate key can not full attribute from other table so that candidate key beyond question superkey but not yet sure on the contrary.
• primary key
• one of [the] attribute from candidate key can be choose/determined to be primary key with three criteria as follows:
1. key more natural to be used as reference
2. key simpler
3. key well guarantee the uniqueness
• alternate key attribute from candidate key not chosen be primary key.
• foreign key be just any attribute that indicate to primary key in other table. foreign key will happen at one particular customer that has kardinalitas one to many (one to many) or many to many (many to many). foreign key usually always put in table that aim to many.
• external key be a lexical attribute (or collection lexical attribute) the values always identify one object instance.
ERD (entity relationship diagram):
• ERD a network model that use wording that kept in system according to abstract.
• difference between DFD and ERD :
1. DFD will be a function network model that be carried out by system
2. ERD be data network model that emphasized in structure and relationship data
elements ERD :
• entity -> in ER diagram entity described with long square form. entity something that there in real system also where does stored data or where found data.
• relationship ->in ER diagram relationship can be described with a lozenged. relationship natural connection that between entity. in general given name with verb base so that make easy to do the customer reading.
• relationship degree -> total entity that participate in one relationship. degree often worn in ERD.
• attribute ->character or characteristics from every entity also relationship
• kardinalitas -> show optimum tupel that can relation with entity in entity other
degree relationship
• unary relationship -> model relationship that between entity that come from entity set same.
• binary relationship ->model relationship that between 2 entity.
• ternary relationship -> be relationship between instance from 3 types entity unilaterally.
Kardinalitas :
• found 3 kardinalitas customer that is :
1. one to one: connection level one to one declared with one incident in entity first, has only one connection with one incident in entity second and on the contrary.
2. one to many or many to one: connection level one to many equal to many to one depending from which direction connection seen. to one incident in entity first can has many connection with incident in entity second, if on the contrary one incident in entity second only can has relation with one incident in entity first.
3. many to many: happen if every incident in a entity has many connection with incident in entity another.
example kardinalitas :
notation (diagram e-r) :
• symbolic notation in diagram ER
1. long square declares collection entity
2. circle declares attribute
3. slit ketupat declare customer collection
4. line as liaison between customer collection with collection entity and collection entity with the attribute
Minggu, 05 April 2009
DFD
Data flow diagram
• called also data flow diagram (DFD)
• describe system distribution into module smaller
• will make user less will realize computer area to will understand system that be done
Diagram context
• consist of one process and describe scope from a system
• be level highest from DFD that describe entire input to system and outpur from system
• system is limitted by boundary (described by line broken offs)
• there may not be any storage (storage)
Zero diagram
• describe process from DFD
• give opinion according to comprehensive hit system that handled, show function or principal process, data current and eskternal entity
• in level this maked data existence storage
• for process is not detailed again in level furthermore so added simbol ‘*’ or ‘p’ by the end of process number
• balance input and output (balancing) between diagram 0 with context diagram must be taked care
Detail diagram
• merupaan diagram that elaborate what process is there in diagram zero or level at on it
• numberization level in DFD:
Name Level Name Diagram Number Proses
0 Context
1 Diagram 0 1.0, 2.0, 3.0, ...
2 Diagram 1.0 1.1, 1.2, 1.3, ...
3 Diagram 1.1 1.1.1, 1.1.2, ...
• in one level best not found more than 7 process and maximal 9, when more so dekomposition
Unitary outside
• something that beyond system, but he gives data into system or give data from system
• symbolized with notation box
• external entity doesn't belong part from system
• nomenclature:
1. terminal name shaped noun
2. terminal may not has name same except the object really same
Data current
• be place currences information
• described with straight line that connect component from system
• data current is showed with arrow direction and line is given name on data current that flow
• data current flows between process, data storage and show data current from data shaped input for system
Data current (2)
• name gift guide:
1. data current name that consist of several word currents related with line continues
2. there may not be any data current the name same and name gift must reflect its contents
3. data current that consist of several elements can be declared with element group
4. koid word use ‘data’ and ‘informasi’ to give name in data current
5. can may be data current name is written complete
Data current (3)
• rule other:
data current name that come into a process may not equal to secretory data current name from process
data flow that step into or out from data storage unnecessary given whose name:
• simple data current and easy understood
• data current describes entire item data
there may not be any data current from terminal to data storage or on the contrary because terminal not part from system, terminal connection with data storage must pass process
Process
process is what done by system
process can cultivate data or data current enters to be data current out
process functioned transformation one or several input data is one or several product data as according to desirable spesification
every has one process or several inputs with produce one or several products
process often also called bubble
Process (2)
process name gift guide:
1. process name consists of verb and noun that reflect process function
2. don't use process word as part from name a bubble
3. there may not be any several process that has names same
4. process must be given number. sequence number can may be follow current or sequence process, but such sequence meaningless number absolutely is sequence process chronologically
Data savings
data storage be existing data repository in system
symbolized with a pair parallel line or two lines wrongly one sides side opened
process can take data from or give data to database
name gift guide:
1. name must reflect data storage
2. when does the name more than one word so be must be given sign continue
Data dictionary
functioned to help system executant to interpret application in detail and organisation all data element that used system according to exactly so that user and has base explanation same about input, product, storage and process
in analysis stage, data dictionary is used as a means of communication between system analyst with user
in system planning stage, data dictionary is used to design input, report and databases
data current in dad has global, explanation detailer visible in data dictionary
Data dictionary (2)
data dictionary holds the followings:
1. data current name: must be registerred so that reader that need furthermore explanation about a data current can look for it easily
2. alias: alias or name other from data can be written if (there are) any
3. data form: used to group data dictionary into its use sewaktu system planning
4. data current: show from which data flows and where does data aim
5. explanation: give explanation about meaning from data current
Balancing in DFD
data current that come into and out from one process must equal to data current that comes into and out from process details in level/stage at under it
data current name that come into and out from one process must equal to data urrent name that enters to into and out from process details
total and name entitas outside from a process must equal to total and name entitas outside from process details
matters that must be payed in DFD that has more than one level:
1. must found balance input and output between one level and level next
2. balance between level 0 and level 1 seen in input/output from data current to or from terminal in level 0, while balance between level 1 and level 2 seen in input/output from data current to/from process concerned
3. data current name, data storage and terminal in every level must same if the object same
Prohibition in DFD
data current may not from entitas outside direct aim entitas outside another without pass a process
data current may not from direct data savings aim to entitas outside without pass a process
data current may not from direct data savings aim another data savings without pass a process
data current from one direct process aims another process without pass a data savings best/bisa may be avoided
• called also data flow diagram (DFD)
• describe system distribution into module smaller
• will make user less will realize computer area to will understand system that be done
Diagram context
• consist of one process and describe scope from a system
• be level highest from DFD that describe entire input to system and outpur from system
• system is limitted by boundary (described by line broken offs)
• there may not be any storage (storage)
Zero diagram
• describe process from DFD
• give opinion according to comprehensive hit system that handled, show function or principal process, data current and eskternal entity
• in level this maked data existence storage
• for process is not detailed again in level furthermore so added simbol ‘*’ or ‘p’ by the end of process number
• balance input and output (balancing) between diagram 0 with context diagram must be taked care
Detail diagram
• merupaan diagram that elaborate what process is there in diagram zero or level at on it
• numberization level in DFD:
Name Level Name Diagram Number Proses
0 Context
1 Diagram 0 1.0, 2.0, 3.0, ...
2 Diagram 1.0 1.1, 1.2, 1.3, ...
3 Diagram 1.1 1.1.1, 1.1.2, ...
• in one level best not found more than 7 process and maximal 9, when more so dekomposition
Unitary outside
• something that beyond system, but he gives data into system or give data from system
• symbolized with notation box
• external entity doesn't belong part from system
• nomenclature:
1. terminal name shaped noun
2. terminal may not has name same except the object really same
Data current
• be place currences information
• described with straight line that connect component from system
• data current is showed with arrow direction and line is given name on data current that flow
• data current flows between process, data storage and show data current from data shaped input for system
Data current (2)
• name gift guide:
1. data current name that consist of several word currents related with line continues
2. there may not be any data current the name same and name gift must reflect its contents
3. data current that consist of several elements can be declared with element group
4. koid word use ‘data’ and ‘informasi’ to give name in data current
5. can may be data current name is written complete
Data current (3)
• rule other:
data current name that come into a process may not equal to secretory data current name from process
data flow that step into or out from data storage unnecessary given whose name:
• simple data current and easy understood
• data current describes entire item data
there may not be any data current from terminal to data storage or on the contrary because terminal not part from system, terminal connection with data storage must pass process
Process
process is what done by system
process can cultivate data or data current enters to be data current out
process functioned transformation one or several input data is one or several product data as according to desirable spesification
every has one process or several inputs with produce one or several products
process often also called bubble
Process (2)
process name gift guide:
1. process name consists of verb and noun that reflect process function
2. don't use process word as part from name a bubble
3. there may not be any several process that has names same
4. process must be given number. sequence number can may be follow current or sequence process, but such sequence meaningless number absolutely is sequence process chronologically
Data savings
data storage be existing data repository in system
symbolized with a pair parallel line or two lines wrongly one sides side opened
process can take data from or give data to database
name gift guide:
1. name must reflect data storage
2. when does the name more than one word so be must be given sign continue
Data dictionary
functioned to help system executant to interpret application in detail and organisation all data element that used system according to exactly so that user and has base explanation same about input, product, storage and process
in analysis stage, data dictionary is used as a means of communication between system analyst with user
in system planning stage, data dictionary is used to design input, report and databases
data current in dad has global, explanation detailer visible in data dictionary
Data dictionary (2)
data dictionary holds the followings:
1. data current name: must be registerred so that reader that need furthermore explanation about a data current can look for it easily
2. alias: alias or name other from data can be written if (there are) any
3. data form: used to group data dictionary into its use sewaktu system planning
4. data current: show from which data flows and where does data aim
5. explanation: give explanation about meaning from data current
Balancing in DFD
data current that come into and out from one process must equal to data current that comes into and out from process details in level/stage at under it
data current name that come into and out from one process must equal to data urrent name that enters to into and out from process details
total and name entitas outside from a process must equal to total and name entitas outside from process details
matters that must be payed in DFD that has more than one level:
1. must found balance input and output between one level and level next
2. balance between level 0 and level 1 seen in input/output from data current to or from terminal in level 0, while balance between level 1 and level 2 seen in input/output from data current to/from process concerned
3. data current name, data storage and terminal in every level must same if the object same
Prohibition in DFD
data current may not from entitas outside direct aim entitas outside another without pass a process
data current may not from direct data savings aim to entitas outside without pass a process
data current may not from direct data savings aim another data savings without pass a process
data current from one direct process aims another process without pass a data savings best/bisa may be avoided
Minggu, 29 Maret 2009
wisdom and design system
before information system is developed, usually beforehand begun with existence a insident and that system development planning. without good system design existence, system development will not such as those which supposed. system design is guide to do system development.
system wisdom
wisdom to develop information system is done by management top, because management wishes for to reaches chances existing unachievable by old ones system or has many weaknesses necessary at improve. for example, some years ago management from mckenson decide wisdom to apply a system design to develop inwrought information system to increase productivity from employees.
system design
after top management decides wisdom to develop information system, before that system is at develops, so necessary planned beforehand. system design concerns estimation from physical needs, worker, and cost that wanted to support from system development. system design usually handled by staff system designer, if staff this is there is no, so planning can be done by system department.
- planning staff has task to do system design based on system wisdom that appointed by management top. when staff this there is no, so the function will be taken to displace by department system developers.
- has task to develop system as according to plan that made ole planning staff and when does this there is no, the function will be taken to displace by system developers consultant outside company.
- has task to operate system that developed by system developers department
system design process
system design process can be grouped to into three principal process, that is:
- plan system projects that done by system designer staff.
- will determine system projects that be developed that done by director committee.
- define system projects that developed by systems analysis.
stages plan system project:
1. determine aim, planning with tactics companies.
2. identify system projects
3. decide system projects target
4. decide system projects obstacle
5. menetu system projects priority.
6. make system design report.
will prepare system projects that be developed
1. indicate team analysis
2. announce system developers project
define system projects that developed
thereby task that must be done by team analysis in this stage:
1. identify to return scope and system project target,
2. do feasibility study,
3. evaluate system project feasibility,
4. make project proposal,
5. ask management sanctions.
do feasibility study
feasibility study a study that be used to menetu is system development proper at go on
or at stop. this watchfulness aims unuk:
1. realize operation from old ones system
2. determine system user needs marginally to can achieve these system target.
3. determine troubleshoots that so that old ones system not yet can achieve aim.
evaluate system project feasibility
five feasibility that can considering:
1. technique feasibility
2. operation feasibility
3. schedule feasibility
4. economy feasibility
5. law feasibility
system wisdom
wisdom to develop information system is done by management top, because management wishes for to reaches chances existing unachievable by old ones system or has many weaknesses necessary at improve. for example, some years ago management from mckenson decide wisdom to apply a system design to develop inwrought information system to increase productivity from employees.
system design
after top management decides wisdom to develop information system, before that system is at develops, so necessary planned beforehand. system design concerns estimation from physical needs, worker, and cost that wanted to support from system development. system design usually handled by staff system designer, if staff this is there is no, so planning can be done by system department.
- planning staff has task to do system design based on system wisdom that appointed by management top. when staff this there is no, so the function will be taken to displace by department system developers.
- has task to develop system as according to plan that made ole planning staff and when does this there is no, the function will be taken to displace by system developers consultant outside company.
- has task to operate system that developed by system developers department
system design process
system design process can be grouped to into three principal process, that is:
- plan system projects that done by system designer staff.
- will determine system projects that be developed that done by director committee.
- define system projects that developed by systems analysis.
stages plan system project:
1. determine aim, planning with tactics companies.
2. identify system projects
3. decide system projects target
4. decide system projects obstacle
5. menetu system projects priority.
6. make system design report.
will prepare system projects that be developed
1. indicate team analysis
2. announce system developers project
define system projects that developed
thereby task that must be done by team analysis in this stage:
1. identify to return scope and system project target,
2. do feasibility study,
3. evaluate system project feasibility,
4. make project proposal,
5. ask management sanctions.
do feasibility study
feasibility study a study that be used to menetu is system development proper at go on
or at stop. this watchfulness aims unuk:
1. realize operation from old ones system
2. determine system user needs marginally to can achieve these system target.
3. determine troubleshoots that so that old ones system not yet can achieve aim.
evaluate system project feasibility
five feasibility that can considering:
1. technique feasibility
2. operation feasibility
3. schedule feasibility
4. economy feasibility
5. law feasibility
Minggu, 08 Maret 2009
Destination Information System Development
Important matter from system development :
• Because problems of the long system, the problem be appear is :
- crummy Settled of the long system because the long system can’t operate with good. Many fraudulent with expressly that result , it’s make money firm not safe.
- Not intentional the wrong can cause truth from data less
- Don’t the efficient data
- Don’t the loyal with firm
• Development organization
Between is information more and more extensive, data volume more increase, principle change new accountancy. Because it change, then the long system not effective again.
• For reaches to chances
Because with development system information, organization can take decision swiftly and make sever by quick.
• existence Instructions (directives) from leadership, for example government regulation
Destination from information system development
• for make easy organization in break problem
• to make easy to get to chances existing
• to make easy to finish existing instructions
by applying information system, hope from a organization as following :
• performance
this measured from reduction and efficient time.
• information
this measured to make easy give information and easy information service.
• economy
with the new system information, hope organization is decrease cost for operation firm.
• Control
With the new system information, hope organization is make easy in detect and repair error from long system.
• Efficiency
Example : Decrease time for do a job in organization
• Services
It is destination fro increase from service system.
Principle from information system development
• System for management
Destination for make easy regulate organization from a firm
• System is big investment
Investigation all alternative(minimize opportunity cost the lost)
• System wants one who educated, not educate formal
• System development have to not massage, can done at random
• Don’t be afraid cancel project, it destination to avoid loss from a organization.
• System documentation, it destination to make easy to see from a system existing
System development life cycle
• life cycle model waterfall a method system the working gradually, in every stage can not return previous step. The step composition is requirements, design, implementation, verification, maintenance. With waterfall method, if step be verification we can’t previous to step design.
• life cycle with method itratif, by using this method our first does with initial planning, then requirement, analysis and design, then implementation, deployment, besides deployment we also do testing, then continued with evaluation. if there deficit or error in system, we can do new planning. this be difference between method waterfall with itratif. itratif can do change if there error in system.
• from life cycle spiral model, first step at does in spiral method concept of requirement that present in stage development, then concept of operation this present in stage plan, stage requirement plan that present in stage determine, risk analysis this present in stage identfy and resolve risk, get a temporary result then that is continued with stage venfication and validation, then development plan, risk analysis, produce a prototype 2, then at continue with venfication and validation, then at continue with test plan, continued again with risk analysis and produce oprational prototype, continued with detailed design, code, integration, test, implementation, and last is done release from system made.
approaches of developing a system
• will approach classic opponent will approach structured will approach this will emphasized that system development success when follow stage at system life cycle.
- pendekatan classic approach in system development that follow stages at system life cycle without supplied with tools and techniques memadai.
- pendekatan structured approach this that begun from beginning year 1970 called with approach structured. approach structured equiped with tools and techniques that wanted in system development so that end result from system that developed be got system so that end result from system the structure will be be defined well and clear.
• approach pieces opponent approaches system.
approach pieces be to approach system development that emphasized at one particular activity or certain application. approach system that pay attention information system as one integration unitary to each activity or the application.
• approach system comprehensive opponent approaches
approach sistem-menyeluruh be to approach menyang system together according to comprehensive. will approach this less synchronized for system complex because difficult to be developed. this be to approach classic approach modulate try broken complex system become some part or simple module, so that system easier will be understood and developed.
• approach opponent far jump approaches to bloom.
approach to jump -jauh apply change according to together use sophisticated technology. this change is many contains risk, because computer technology so fast bloom and to year coming be worn out. approach this too expensive, because need investment at the same moment. approach to bloom to apply sophisticated technology just for applications that need at that moment and then be developed for periods next will follow the need as according to existing technology development
meaning of methodology, method and algorithm
• methodology is unitary from methods, procedures, job concepts, rules that used by a science, art, or discipline the other
• method is a steps to in methodology
• algorithm is sequence procedure to break problem.
three classifications of development methodology
• functional decomposition methodologies
this methodology constitute in solution from system into sub system smaller. belong into group methodologies this:
- HIPO (hierarchy plus-process-output)
- Stepwise refinement (SR) or iterative stepwise refinement(ISR)
- Information-hiding
• Data oriented methodologies
- Data flow methodologies
this methodology is in general is based in solution from system intoes modules based on from type element data and module logic behaviour in system
- Data structure oriented methodologies
this methodology emphasizeds structure from input and output at system. mask in this methodology: jsd (jakson's systems development) and w/o(warnier/orr)
tools for developing a system
• system development tool:
HIPO diagram, used in metodelogi HIPO
Data flow diagram, used in system analysis and design S
Structured chart, used at method wanier/orr
Jakson's diagram, used at methodology jakson's system development
Techniques used in developing a system
techniques that can be used :
• technique management project, that is CPM(critical part method) and PERT (program evaluation and review technique). This technique used in project scheduling.
• Fact finding techniques, that is technique that can be used to gather fact and find data in activity study existing activity.
• technique analysis cost/benefit (cost-effectiveness analisys or cost-benefit analysis)
• technique to run meeting
• technique inspection/walkthrough
system analyst and a programmer
• system analysis one who analysis system (study that problems and determine system user needs) identify solution that have occasion
• a programming one who write program codes into computer system. where is code at write by virtue of analysis from a system analysis.
mention what are the knowledge a system analyst should posses
• knowledge and skill about technique processing data
• knowledge about business in general
• knowledge about quantitative method
• trouble-shooting skill
• skill in communicate with staff
• skill in build connection with staff
teken from :
* analisis & desain system
* slide Part 2 - PENGEMBANGAN SISTEM.ppt
• Because problems of the long system, the problem be appear is :
- crummy Settled of the long system because the long system can’t operate with good. Many fraudulent with expressly that result , it’s make money firm not safe.
- Not intentional the wrong can cause truth from data less
- Don’t the efficient data
- Don’t the loyal with firm
• Development organization
Between is information more and more extensive, data volume more increase, principle change new accountancy. Because it change, then the long system not effective again.
• For reaches to chances
Because with development system information, organization can take decision swiftly and make sever by quick.
• existence Instructions (directives) from leadership, for example government regulation
Destination from information system development
• for make easy organization in break problem
• to make easy to get to chances existing
• to make easy to finish existing instructions
by applying information system, hope from a organization as following :
• performance
this measured from reduction and efficient time.
• information
this measured to make easy give information and easy information service.
• economy
with the new system information, hope organization is decrease cost for operation firm.
• Control
With the new system information, hope organization is make easy in detect and repair error from long system.
• Efficiency
Example : Decrease time for do a job in organization
• Services
It is destination fro increase from service system.
Principle from information system development
• System for management
Destination for make easy regulate organization from a firm
• System is big investment
Investigation all alternative(minimize opportunity cost the lost)
• System wants one who educated, not educate formal
• System development have to not massage, can done at random
• Don’t be afraid cancel project, it destination to avoid loss from a organization.
• System documentation, it destination to make easy to see from a system existing
System development life cycle
• life cycle model waterfall a method system the working gradually, in every stage can not return previous step. The step composition is requirements, design, implementation, verification, maintenance. With waterfall method, if step be verification we can’t previous to step design.
• life cycle with method itratif, by using this method our first does with initial planning, then requirement, analysis and design, then implementation, deployment, besides deployment we also do testing, then continued with evaluation. if there deficit or error in system, we can do new planning. this be difference between method waterfall with itratif. itratif can do change if there error in system.
• from life cycle spiral model, first step at does in spiral method concept of requirement that present in stage development, then concept of operation this present in stage plan, stage requirement plan that present in stage determine, risk analysis this present in stage identfy and resolve risk, get a temporary result then that is continued with stage venfication and validation, then development plan, risk analysis, produce a prototype 2, then at continue with venfication and validation, then at continue with test plan, continued again with risk analysis and produce oprational prototype, continued with detailed design, code, integration, test, implementation, and last is done release from system made.
approaches of developing a system
• will approach classic opponent will approach structured will approach this will emphasized that system development success when follow stage at system life cycle.
- pendekatan classic approach in system development that follow stages at system life cycle without supplied with tools and techniques memadai.
- pendekatan structured approach this that begun from beginning year 1970 called with approach structured. approach structured equiped with tools and techniques that wanted in system development so that end result from system that developed be got system so that end result from system the structure will be be defined well and clear.
• approach pieces opponent approaches system.
approach pieces be to approach system development that emphasized at one particular activity or certain application. approach system that pay attention information system as one integration unitary to each activity or the application.
• approach system comprehensive opponent approaches
approach sistem-menyeluruh be to approach menyang system together according to comprehensive. will approach this less synchronized for system complex because difficult to be developed. this be to approach classic approach modulate try broken complex system become some part or simple module, so that system easier will be understood and developed.
• approach opponent far jump approaches to bloom.
approach to jump -jauh apply change according to together use sophisticated technology. this change is many contains risk, because computer technology so fast bloom and to year coming be worn out. approach this too expensive, because need investment at the same moment. approach to bloom to apply sophisticated technology just for applications that need at that moment and then be developed for periods next will follow the need as according to existing technology development
meaning of methodology, method and algorithm
• methodology is unitary from methods, procedures, job concepts, rules that used by a science, art, or discipline the other
• method is a steps to in methodology
• algorithm is sequence procedure to break problem.
three classifications of development methodology
• functional decomposition methodologies
this methodology constitute in solution from system into sub system smaller. belong into group methodologies this:
- HIPO (hierarchy plus-process-output)
- Stepwise refinement (SR) or iterative stepwise refinement(ISR)
- Information-hiding
• Data oriented methodologies
- Data flow methodologies
this methodology is in general is based in solution from system intoes modules based on from type element data and module logic behaviour in system
- Data structure oriented methodologies
this methodology emphasizeds structure from input and output at system. mask in this methodology: jsd (jakson's systems development) and w/o(warnier/orr)
tools for developing a system
• system development tool:
HIPO diagram, used in metodelogi HIPO
Data flow diagram, used in system analysis and design S
Structured chart, used at method wanier/orr
Jakson's diagram, used at methodology jakson's system development
Techniques used in developing a system
techniques that can be used :
• technique management project, that is CPM(critical part method) and PERT (program evaluation and review technique). This technique used in project scheduling.
• Fact finding techniques, that is technique that can be used to gather fact and find data in activity study existing activity.
• technique analysis cost/benefit (cost-effectiveness analisys or cost-benefit analysis)
• technique to run meeting
• technique inspection/walkthrough
system analyst and a programmer
• system analysis one who analysis system (study that problems and determine system user needs) identify solution that have occasion
• a programming one who write program codes into computer system. where is code at write by virtue of analysis from a system analysis.
mention what are the knowledge a system analyst should posses
• knowledge and skill about technique processing data
• knowledge about business in general
• knowledge about quantitative method
• trouble-shooting skill
• skill in communicate with staff
• skill in build connection with staff
teken from :
* analisis & desain system
* slide Part 2 - PENGEMBANGAN SISTEM.ppt
Jumat, 20 Februari 2009
Basic Concept of Information Systems Analysis and Design
Before studying what that Information Systems Analysis and Design, first we have to know what that system and what that information.
WHAT IS SYSTEM?
There are two approaching to definition of system:
1. Definition of system based on approach of procedure
According to this approach, system interpreted by as a working network from procedures which is interaction and work along to finish a specific-purpose or goal. A procedure is a correct sequences of instruction steps explaining what have to be done, who have to do, when have to be done and how to do that.
2. Definition of system based on approach of element
According to this approach the definition of system is a set of elements which is have interaction to reach specific-purpose or goal.
CHARACTERISTIC OF SYSTEM
Characteristic a system can be explained as follows:
1. Components
Consist of a number of components which interact, what each other working along to form an unity. The example is Supra System that is a larger ones system.
2. Boundary
A system has a boundary to limiting system with environmental or other system outside its.
3. Environments
Environment is a media link between a subsystem with other subsystem.
4. Input
Entered energy into system can in the form of treatment input and signal input. The treatment input is entered energy system to can walk. While signal input is energy which in process to yield output.
5. Output
The result from processed energy and classified is become an output which good for and rest of dismissal.
6. Process
Process is the change an input become output.
7. Target (objective)/goal
Otherwise have the target then system operation there will be no utilizing of. The system is told succeed if it has reach the target/its goal.
The Classification Of System
a. Deterministic System
The Certain system operate with behaviour which have earned can be predicted, interaction between its sharess can be detected categorically so that its output can be forecasted. for example of : Computer programe, executing precisely as according to its instruction network. System of pay, and others.
b. Probabilistic System
The System which is input and its process can be defined, but yielded output cannot be determined categorically; ( always there is a little mistake / deviation to forecast of the way system). for Example : marketing system)
c. Open System
The system that relation and effect external environment .This system accept input and yield output for external environment / the other sub system, so that have good operation system. This system tend to measure up to adaptation, can adapt to its environment so that can continue its.
d. Closed System
The System Physical where the process that happened do not experience of transfer of items, information or energy with environment outside system. This system work automatically without existence of interfere in of external side of it.
e. Relatively Closed System
The closed System but doesn't closed at all to accept other influences. This system in its operation can accept influence from outside which have been defined in certain boundarys.
f. Artificial System
The System imitating occurence in system. This system is formed pursuant to occurence in nature where human being unable to do it. Equally imitat exist in nature.
g. Natural System
The natural System is occurence in nature. for Example of : sea, solar system and others.
h. Manned System
The System explanations of behaviour covering human being taking part in. This system can be depicted in way of as follows:
The System of Human being focus the relations between human being
The System of Human being - Machine, System which involve machine to a target
The Machine System, automatic system where human being have duty to start and finish system, meanwhile human being entangled also to monitor system.
Information
Data is fact. Information is data that processed become better form and more meaning to accept it. If data is not useful to accept it so the data cannot be referred as by information.
QUALITY OF INFORMATION
To get information with quality, then information must have:
*
Accurately
Information free from mistakes and doesn't deflect or mislead
*
Punctually
Incoming information at receiver may not lose time
*
Relevantly
Information is have benefit for its usage.
Information will be valuable if big added significance of expense get it
WHAT IS SYSTEM?
There are two approaching to definition of system:
1. Definition of system based on approach of procedure
According to this approach, system interpreted by as a working network from procedures which is interaction and work along to finish a specific-purpose or goal. A procedure is a correct sequences of instruction steps explaining what have to be done, who have to do, when have to be done and how to do that.
2. Definition of system based on approach of element
According to this approach the definition of system is a set of elements which is have interaction to reach specific-purpose or goal.
CHARACTERISTIC OF SYSTEM
Characteristic a system can be explained as follows:
1. Components
Consist of a number of components which interact, what each other working along to form an unity. The example is Supra System that is a larger ones system.
2. Boundary
A system has a boundary to limiting system with environmental or other system outside its.
3. Environments
Environment is a media link between a subsystem with other subsystem.
4. Input
Entered energy into system can in the form of treatment input and signal input. The treatment input is entered energy system to can walk. While signal input is energy which in process to yield output.
5. Output
The result from processed energy and classified is become an output which good for and rest of dismissal.
6. Process
Process is the change an input become output.
7. Target (objective)/goal
Otherwise have the target then system operation there will be no utilizing of. The system is told succeed if it has reach the target/its goal.
The Classification Of System
a. Deterministic System
The Certain system operate with behaviour which have earned can be predicted, interaction between its sharess can be detected categorically so that its output can be forecasted. for example of : Computer programe, executing precisely as according to its instruction network. System of pay, and others.
b. Probabilistic System
The System which is input and its process can be defined, but yielded output cannot be determined categorically; ( always there is a little mistake / deviation to forecast of the way system). for Example : marketing system)
c. Open System
The system that relation and effect external environment .This system accept input and yield output for external environment / the other sub system, so that have good operation system. This system tend to measure up to adaptation, can adapt to its environment so that can continue its.
d. Closed System
The System Physical where the process that happened do not experience of transfer of items, information or energy with environment outside system. This system work automatically without existence of interfere in of external side of it.
e. Relatively Closed System
The closed System but doesn't closed at all to accept other influences. This system in its operation can accept influence from outside which have been defined in certain boundarys.
f. Artificial System
The System imitating occurence in system. This system is formed pursuant to occurence in nature where human being unable to do it. Equally imitat exist in nature.
g. Natural System
The natural System is occurence in nature. for Example of : sea, solar system and others.
h. Manned System
The System explanations of behaviour covering human being taking part in. This system can be depicted in way of as follows:
The System of Human being focus the relations between human being
The System of Human being - Machine, System which involve machine to a target
The Machine System, automatic system where human being have duty to start and finish system, meanwhile human being entangled also to monitor system.
Information
Data is fact. Information is data that processed become better form and more meaning to accept it. If data is not useful to accept it so the data cannot be referred as by information.
QUALITY OF INFORMATION
To get information with quality, then information must have:
*
Accurately
Information free from mistakes and doesn't deflect or mislead
*
Punctually
Incoming information at receiver may not lose time
*
Relevantly
Information is have benefit for its usage.
Information will be valuable if big added significance of expense get it
Langganan:
Postingan (Atom)
