the piopio

Jeong Yong Hwa [CNBLUE] - Banmal Song Lyrics and Translation

2011-10-28T21:05:00.000-07:00

maen cheoeum neoreul bodeon nal
sujub giman hadeon neoye malgeun misodo
oneuri jinamyeon gakkawo jilgeoya
maeil seolleneun gidaereul hae

museun mareul geonde bolkka
eotteohke hamyeon niga useo julkka
soneul geonde boda eosaek hae jilkka bwa
meotjjeok eun useum man useo bwa

uri seoro banmal haneun sa iga dwe gireul
ajik jogeum seotureugo eosaek hande do
gomawo yo raneun maltu daeshin
jomdeo chinhage mareul hae jullae

uri seoro banmal haneun sa iga dwel geoya
hangeol eumsshik cheoncheonhi dagawa
ijen nae dununeul bara bomyeo mareul hae jullae
neol saranghae

neowa ye soneul jabdeon nal
shimjangi meomchu deuthan gibun deure
museun mal haetneunji gieok jocha anna
manyang seolle neun gibun ingeol

uri seoro banmal haneun sa iga dwe gireul
ajik jogeum seotureugo eosaek hande do
gomawo yo raneun maltu daeshin
jomdeo chinhage mareul hae jullae

uri seoro banmal haneun sa iga dwel geoya
hangeol eumsshik cheoncheonhi dagawa
ijen nae dununeul bara bomyeo, mareul hae jullae
neol saranghae

uri seoro saranghaneun sa iga dwe gireul
jabeun duson yeongwonhi nohji anheul kkeoya
bara boneun neoye nunbit soge
haengbokhan misoman itgil barae

uri seoro saranghaneun sa iga dwel kkeoya
akkyeo jugo pyeonhi gidaemyeon dwe
neoreul boneun naye du nun bitchi
malhago isseo
neol saranghae

TRANSLATION

The day when I first saw you

Your bright smile full of shyness
we’ll get closer after today
Every day, I have heart-fluttering expectations

What to say to you
How to get you to laugh
I fear it’ll get awkward when I try to hold your hand
All I can do is smile shyly

Hopefully we can speak banmal to each other
Even though it’s still awkward and unfamiliar
Instead of saying ‘thank you’
Talk to me in a friendlier way

Hopefully we can speak banmal to each other
You walk towards me slowly, step by step
Now look at my two eyes and tell me
I love you

The day when I held your hand
I felt my heart stop beating
I don’t even remember what I said
All I feel is a flutter in my stomach

Hopefully we can speak banmal to each other
Even though it’s still awkward and unfamiliar
Instead of saying ‘thank you’
Talk to me in a friendlier way

Hopefully we can speak banmal to each other
You walk towards me slowly, step by step
Now look at my two eyes and tell me
I love you

Hopefully we can fall in love with each other
I’ll never let go of your two hands from my grasp
The light of your eyes, gazing at me
I hope there will only be joyful smiles

We can probably fall in love with each other
We can lean on one another and take care of each other
Looking into your eyes, my two eyes
They’re talking to you
I love you

Lalala...Love Song

2009-08-05T20:16:00.000-07:00

Lalala...Love Song

By: As One - Worlds Within Ost

a simply song plays in my memory

in the morning sun i take it with my toast and tea

who'd a thought that i love whould suddenly

sing to me happily la didi~ ~

just when i thought it was fate

more than once fate was surely dealyed

then you came certain as the rain

pouring down on me love's destiny

a simply song plays in my memory

in the morning sun i take it with my toast and tea

who'd a thought that i love whould suddenly

sing to me happily la didi~ ~

lalalalala ~ ~

i sing this song to you

lalalalala ~ ~

dedicated this song just for you

gonna the test when i'd said

in the room mean that talk queily

wishing for something even more

tell a friend when i seem like a dream

a simply song plays in my memory

in the morning sun i take it with my toast and tea

who'd a thought that i love whould suddenly

sing to me happily la didi~ ~

lalalalala ~ ~

i sing this song to you

lalalalala ~ ~

dedicated this song just for you

when u feel my one and only where are dream for us

lalala..

i song this sing for us

lalala..

it's you when dream in up

a strugling ever love and never wake

when the hard studies feel with be

a simply song plays in my memory

in the morning sun i take it with my toast and tea

who'd a thought that i love whould suddenly

sing to me happily la didi~ ~

Information Systems Analysis and Design [Part-7]

2009-05-03T02:45:00.000-07:00

AN EXERCISE

I have task, that is to normalize the ER-Diagram below and provide the representation of the physical table.

that diagram is have anomaly entity, then i try to solve that as follows:
1. There’s no cardinality between entity BAGIAN and PROYEK. It should have been 1-N from BAGIAN to PROYEK. it is because of that one BAGIAN may have many PROYEK, and one PROYEK may only have one BAGIAN.
2. The ternary relationship between entity PEGAWAI, PROYEK, & TANGGUNGAN seems strange. It’s legitimate if entity PEGAWAI has a relationship with TANGGUNGAN (TANGGUNGAN will be the weak entity because it’s Dependant with the existence of the PEGAWAI). But it’s also has a relation with PROYEK, and supported with the existence of relation between PEGAWAI an PROYEK. Then I will delete the ternary relationship between entity PEGAWAI and TANGGUNGAN and change them only with binary relationship.
3. To determine the mapping later, we need to fix the relation PIMPIN between entity PEGAWAI and BAGIAN to gain the foreign key. Because of one BAGIAN must be managed at least by one PEGAWAI, and one PEGAWAI must not managing one BAGIAN.
Here is the fixed ER diagram:
Then I try to make the Mapping of the ER-Diagram above:

After that, I make the normalization for 1NF as follows :

For table TANGGUNGAN and KERJA, it don't need to be normalization because they don't have a primary key.
The normalization above has also been the 2NF normalization.

Then for the 3NF normalization, we should determine which of the attribute that has a transitive dependency. There is:

Information Systems Analysis and Design [Part-6]

2009-04-24T02:01:00.000-07:00

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 : AB or A x --> B are opposite of previous notation.

From the table above, we can explain that:

Functional Dependency:

• NRP name

• Subject, NRP Grade

Non Functional Dependency:

• Subject NRP

• NRP Grade

Functional Dependency from the table value

NRP Name

Because of each value of NRP that same, then the value of Name also same.

{Subject, NRP} Grade

Because of attribute Grade is depend on Subject and NRP jointly. In other mean for Subject and same NRP, therefore Grade also same, because Subject and NRP are key (get unique character)

– Subject NRP

– NRP Grade

First Normal Form - 1NF

A table is said exist on normal form I if it don't exist on unnormalized form table, where is happening multiplexing a sort field and enabling available field that null (empty).

For example College Student Data as follows:

ID	NAME	HOBBY
12020001	Feri Wijantara	Football, reading comics, swimming
12020013	Leoni WS	Cooking, singing
12020015	Rion Saputra	tailor, making bread

ID	NAME	HOBBY1	HOBBY2	HOBBY3
12020001	Feri Wijantara	Football	reading comics	swimming
12020013	Leoni WS	Cooking	singing
12020015	Rion Saputra	Tailor	making bread

The tables above are ineligible for 1NF. Decomposition becomes:

- Collegian table:

ID	NAME
12020001	Feri Wijantara
12020013	Leoni WS
12020015	Rion Saputra

- Hobby table:

ID	HOBBY
12020001	Football
12020001	reading comics
12020001	swimming
12020013	Cooking,
12020013	singing
12020015	tailor
12020015	making bread

Second Normal Form - 2NF

2NF's normal form is accomplished in one table if have accomplished 1NF's form, and all attribute besides primary key, as whole to have Functional Dependency on primary key. One table will not accomplishes 2NF, if there is attribute which its dependency (Functional Dependency) just have partial character only (just depend on a part of primary key). If anything attribute that have no dependency for primary key, therefore that attribute have to move or is removed. Functional dependency X Y is said full if erasing an attribute A of X its mean that Y no longer functional dependent. Functional dependency X Y is said partial if erases an A's attribute of X matter Y still functional dependent. Relationship scheme r on 2NF form if each attribute non primary key A R full dependent functionally on primary key R.

This following table accomplishes 1NF, but excluding 2NF:

ID	Name	Address	Subject_code	Subject	Sks	Grade
0608605087	Leoni WS	Jl. Celagi Basur	DM	Data Mining	3	A
0608605013	Feri Wijantara	Jl. Sriwijaya	GIS	Sistem Informasi Geografis	3	B
0608605087	Leoni WS	Jl. Celagi Basur	GIS	Sistem Informasi Geografis	3	A
0608605200	Rion Saputra	Jl. Penguin	GIS	Sistem Informasi Geografis	3	C
0608605087	Leoni WS	Jl. Celagi Basur	MP	Metodologi Penelitian	2	A
0608605200	Rion Saputra	Jl. Penguin	MP	Metodologi Penelitian	2	B

That table is Not accomplishing in 2NF's form, because {ID, Subject_Code} that is looked on as primary key meanwhile:

{ID, Subject_code} Name

{ID, Subject_code}Address

{ID, Subject_code} Subject

{ID, Subject_code} Sks

{ID, Subject_code} Grade

That table needs to decomposition becomes many table that measures up 2NF.

The Functional dependency as follows:

{ID, Subject_code} Grade (fd1)

ID{Name, Address} (fd2)

Subject_code {Subject, Sks} (fd3)

So:

fd1 (ID, Subject code, Grade) Appreciative table

fd2 (ID, Name, Address) Collegian table

fd3 (Subject code, Subject, Sks) Subject's table

Third Normal Form - 3NF

3NF's normal form is accomplished if have accomplished 2NF's form, and if no attribute non primary key that have dependency to attribute non primary key another (transitive dependency).

This Following collegian table measures up 2NF, but doesn't accomplish 3NF:

ID	Name	Address	City	Province	PostalCode
0608605087	Leoni WS	Jl. Celagi Basur	Badung	Bali	80978
0608605013	Feri Wijantara	Jl. Sriwijaya	Gianyar	Bali	80999
0608605139	Fernindya Putri	Jl. Kura-kura	Denpasar	Bali	81233
0608605200	Rion Saputra	Jl. Penguin	Bangli	Bali	80612

Since is still exist the attribute non primary key (namely City and Province) that have dependency to attribute non primary key another one (namely PostalCode):

PostalCode {City, Province}

So that table need to be decomposition becomes:

Collegian (ID, Name, Street, PostalCode)

PostalCode( PostalCode, Province, City)

Boyce-Codd Normal Form (BNCF)

Boyce Codd Normal Form has stronger compulsion of third Normal form. To become BNCF, relationship shall in first Normal form and each attribute is forced dependent on function on attribute super key.

On example hereunder is exists Seminar relationship, Prime key is NPM + seminar.

Student may take one or two seminar. Each seminar needs 2 counselors and each student led by one of between 2 that seminar counselor. Each counselor just may take one seminar only. On this example NPM and seminar points out a Counselor.

Seminar Relationship

NPM	Seminar	Counselor
1000	S100	Leoni
1001	S100	Feri
1002	S101	Rion
1001	S101	Rion
1003	S101	Nelly

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:

Counselor Relationship

Counselor	Seminar
Leoni	S100
Feri	S100
Rion	S101
Nelly	S101

Seminar-Counselor Relationship

NPM	Counselor
1000	Leoni
1001	Feri
1002	Rion
1001	Rion
1003	Nelly

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

Information Systems Analysis and Design [Part-5]

2009-04-18T08:04:00.000-07:00

Database and entity relationship diagram

The definition of database

Database can be definition by collection of data which stored in magnetic disk, optical disk or other secondary storage. In other word database is collection of data which is linked one to other of an enterprise (factory, governmental institution, or private section). For example is in manufacture company, the database include production planning data, actual production data, data ordering material. And in hospital database include of data of patient, doctor, nurse, etc.

Database management system (DBMS)

Database management System is database collection with software application in based of database. This application programs is use for accessing and maintaining the database. The first aim of DBMS is to preparing an easy and efficient environment for using, collecting and storing data and information.

Definition of bit, byte, field

>> Bit: is the smaller part of data, which contain of value 1 or 0

>> Byte: collection of bits that of a kind

>> filed: collection of byte that of a kind, which in database is called "attribute".

Attribute or field

Attribute or field is a characteristic of entity, which preparing detailed explanation about that's entity. A relation also could have attributed.

Example of attribute:

- Attribute of motor cycle is number plate, color, kind, etc.

- Attribute of book is title, kind, total page, author, etc.

Type of attribute

1. Single vs. multivalued

Single: only can fill by one value

multivalued: can fill with more one value with the same of kind

2. Atomic vs. composition

Atomic: can not divided into smaller attribute

Composition: boundless from some smaller attribute

3. Derived attribute

Derived attribute is an attribute which its value can be produced from other attribute

4. Null value attribute

Null value attribute is an attribute with no value for a record

5. Mandatory value attribute is an attribute which must have value

Record or Tuple

Record is a line of data in a relationship. It does consist of collection attribute, where the attributes is related one to other to give detailed information of the entity or relation.

Entity or file

File is a collection of record that of a kind and having same element, same attribute however different in their data value.

Type of file:

In processing application, file can be categorized such as:

- Parented file

- Transaction file

- Report file

- History file

- Protector file

- Work file

Domain

Domain is collection of values which enabled to stay in one or more attribute. Every attribute in a relational database is defined as a domain

Key of element data

Key is the element of record which used to find the record when accessing or can also used to identify every entity / record / row.

Kind of key:

* Super key is one or more attribute from a table which can be used for identifying entity / record from table uniquely

* Candidate key is super key with minimum attribute. Candidate key may not contain attribute of other table so that the candidate is super key, but not the contrary

* Primary key

One of the attribute of candidate key can be selected / determined into primary key with 3 criteria:

- The key is more natural for use as reference

- The key is simpler

- The key is unique

* Alternate key

Alternate key is attribute of candidate key which is not chosen become primary key

* Foreign key

Foreign key is any attribute subjecting to primary key at other tables. Foreign key will be happened in a relation which have one to many cardinality or many to many cardinality. Foreign key usually put at the table which direct to many cardinality.

* External key

External key is lexical attribute or collection of lexical attribute which values always identify one object instance

ERD (entity relationship diagram)

ERD is a network model that uses word order is stored in the system of abstract

The different between DFD and ERD:

- DFD is a network functions model that will be implemented by the system

- ERD is a network data model that emphasizes the on the structure and relationship data

Elements in ERD

Elements in ERD include:

* Entity

In the ER Diagram, entity is described with the form of a rectangle. Entity is something that exists in the real system and the abstract where the data stored or where there are data.

* Relationship

In the ER diagram, the relationship can be described with a rhomb. Relationship is a natural relation that occurs between entities. In a general way given by name by vocabulary so that making it easier to do the reading of relation.

* Relationship degree

Relationship degree is the number of entities which participating in a relationship. Degree is unit which is often used in the ERD.

* Attribute

Attribute is the nature or characteristics of each entity and relationship

* Cardinality

Cardinality indicates the maximum number of record/tuple that can be relation with the entity on the other entity

Degree of relationship

* Unary relationship is the relationship model between the entity originating from the same entity set.

* Binary relationship is the relationship model between 2 entities

* Ternary relationship is a relationship between the instances of 3 types of entities is unilateral

Cardinality

There are three of cardinality relationship, which is:

* One to one

Level one to one relationship stated with one event in the first entity, only had one relationship with one event in the second entities and conversely.

Example:

*One to many or many to one

Level one to many relationship is the same as the many to one depending on the direction from which the relationship have to seen. For an event on the first entity, it can have many relationships with the event on the second entity, if conversely the event in second entities only gets a relationship with one event on the first entity.

Example:

* Many to many

happening if each event on one entities has a many relationship with event on another entities.

Example:

Notation in ER-Diagram

The notation symbol of ER-Diagram is:

• Length square declare for entities gathering

• Circle declares for attribute

• Rhomb declares for relationship gathering

• Lining as connecting among relationship gathering with entities gathering and Entities Gathering with its attribute

References:
1. Agus Sanjaya ER, S.Kom, M.Kom, slide presentation : Database and ER-Diagram

BRISINGR

2009-04-03T04:53:00.000-07:00

Ini novel yang baru aja selesai ku baca setelah bergumul dengan tugas-tugas kuliah yang numplek akhirnya bisa menikmati baca niy novel ;P!

Brisingr adalah buku ketiga dari trilogi Warisan yang ditulis oleh Christopher Paolini, buku pertamanya adalah ERAGON kemudian ELDEST (Tapi ternyata gw salah!!! Setelah tak baca sampai akhir masih ada lanjutannya, berarti niy novel bukan trilogi toh???)

Dalam novelnya yang ketiga ini masih menceritakan tentang perjuangan eragon si penunggang naga dengan naganya yang bernama Saphira. masih juga tentang perlawanan kaum varden yang menentang kekuasaan raja kejam bernama Galbatorix.

Dalam novel ini diceritakan Eragon bersama Roran pergi mencari Katrina yang ditawan oleh para Ra'zackemudian ia menikahkan Roran dan Katrina. Eragon juga menepati janjinya untuk menghapuskan kutukan pada elva namun tidak sepenuhnya berhasil. Kemudian ia mengikuti pemilihan raja kurcaci karena raja sebelumnya yaitu Hrothgar telah tewas dalam pertempuran di daratan membara, ia bersama saphira memperbaiki Ishdar Mitrim di Farthen dur saat penobatan Orik menjadi raja kurcaci ke 44.

Setelah ritual penobatan raja kurcaci, eragon dan saphira balik ke Elesmera untuk bertemu dengan gurunya yang juga penunggang naga yaitu Oromis si cacat yang utuh. Oromis memberitahukan bahwa ayah Eragon bukanlah Morzan, melainkan Brom. Setelah Zar'oc diambil oleh saudara tiri Eragon yaitu Murtagh ia berniat membuat pedang baru yang sesuai dengan dirinya untuk itu ia mencoba untuk bertemu Rhunon si pandai besi elf. Eragon tidak mempunyai pedang yang layak untuk seorang penunggang. Maka ia teringat nasehat Solembum (kucing jadi-jadian) bahwa ketika ia membutuhkan senjata ia dapat mencarinya dibawah akar pohon Menoa. Setelah sempat bersitegang dengan penunggu pohon akhirnya eragon mendapatan brightsteel yang digunakan sebagai bahan membuat pedang tersebut, Rhunon-elda membantunya membuat pedang penunggang yang kemudian diberi nama BRISINGR. Pedang ini menyala setiap Eragon menyebut namanya. Hari terakhir Glaedr memberitahukan kelemahan Golbatorix dan rahasia tentang eldunari yaitu jantungnya jantung naga. Eldunari milik Glaedr diserahkan kepada Saphirauntuk membantu mereka melawan galbatorix. Oromis pun memutuskan untuk memperlihatkan diri di depan Golbatorix dan ikut berperang melawannya secara langsung.

Oromis dan Glaedr melawan Murtagh bersama naganya Thorn di Gil'ead, tiba-tiba Galbatorix menampakan diri melalui Murtagh dan membunuh Oromis. Eragon yang saat itu bertarung bersama Arya melawan Shade melihat pembunuhan itu dalam benaknya. Akhirnya Eragon dan Saphira menjadi penunggang terakhir dan sendirian yang harus melawan Golbatorik.

Novel ini masih berlanjut ke bukunya yang ke-empat...
Duwh.. jadi penasaran...

...buku yang membuat saya rela bergadang.
----The Washington Post

Penuh dengan adegan pertempuran seru yang mengombinasikan sihir dan ilmu perang tradisional...
----Children's Literature

Judul: Brisingr
Pengarang : Christopher Paolini
Penerbit edisi Bahasa Indonesia: Gramedia Pustaka Utama

Information Systems Analysis and Design [Part 4]

2009-04-03T04:29:00.000-07:00

DATA FLOW DIAGRAM (DFD)

Data flow diagram also called Data Flow Diagram (DFD). Data flow diagram is use to figuring system division into smaller module. DFD can facilitate user that insufficiently understand computer's area for understanding system who will be worked.

CONTEXT DIAGRAM

Context diagram is consisting of one process and figures scope of a system. That is supreme level from DFD that figuring all input goes to system and output of system. In context diagram, stored (storage) is not available.

ZERO DIAGRAMS

Zero diagrams are use to figuring process from DFD. The diagram can giving views thoroughly concerning handled system, show function or aught main process, data flow and external entity. On this level is enabled to marks sense data storage. For a process that don't elaborated again on succeeding level then was enhanced symbol ‘*’ or ‘p’ by the end of process numbers. Balancing of input and output among zero diagram and context diagram must be maintained.

DETAILS DIAGRAM

Details diagram that describes the process what’s aught on zero diagram or level on it.

Numbering level on DFD:

Level’s name	Diagram’s name	Process number
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 it is better to have no more than 7 processes and maximal 9 process, if more than that, and then should to be done decomposition.

SPECIFICATION PROCESSES

Each process on DFD shall have process specification. On top level method that is utilized to figure the process can by use of descriptive sentence. At more level detailed that is at lowermost process (primitive functional) requiring the specification of more structure. Specification of processes will be guidance for programmer in making program (coding). Method that is utilized in specification processes are breakdown of process in shaped story, decision table and decision tree.

EXTERNAL ENTITY

An external entity is a source or destination of a data flow which is outside the area of study or something that beyond system, but it gives data into system or gives data from system. Only those entities which originate or receive data are represented on a business process diagram. External entity is symbol with notation box. External entity is excluding part of system.

Rules for Naming:

- Terminal name as noun

- Terminal can not have a same name but the object is really same

DATA FLOW

A data flow shows the flow of information from its source to its destination. A data flow is represented by a line, with arrowheads showing the direction of flow. Information always flows to or from a process and may be written, verbal or electronic. Each data flow may be referenced by the processes or data stores at its head and tail, or by a description of its contents.

Dataflow notations:

Guideline to naming:

1. Name of Data's flow which consisting of several word's flow connected by interlocking lines

2. No data's flow which its have same name, and naming shall reflect its content

3. Data flow that consisting of several element gets to be declared with element group

4. Avoid of using word ‘ data ’ and ‘ information ’ to naming on data flow

5. As much as can the name of data flow is written completed

other rule:

· name of Data flow which turn in at a process may not same by the name of secretory data flow of that process.

· data flow that ingoing goes to or out from data storage not necessarily been given name if:

o Simple data flow and perspicuous

o Data flow figures all item's data

· there is no data flow from terminal to data storage or on the contrary because the terminal is not part of system, terminal relationship with data storage shall pass through process

PROCESS

The process is also often called bubble. Process is what does be worked by system. A process transforms incoming data flow into outgoing data flow. A process shows a transformation or manipulation of data flows within the system. Each process has one or many entries and resulting one or many outputs.

Guideline to naming processes:

* Name processes consisting of verb and noun that reflect that process function

* Don't utilize the word 'process' as part of name a bubble

* there is no many process that have same name

* Process shall be numbered. Number thread as much as can following the flow or process thread, but such number thread doesn't mean absolutely representing process thread chronologically

Process Notations

DATA STORAGE

Data storages are repositories of data in the system. They are sometimes also referred to as files. It is represented by a pair of parallel lines or two lines with one of the side open. Process can take data from or gives data to database

Guideline to naming:

· Name shall reflect data storage

· If its name more than one word then has to be hyphened

SYMBOLS USED ON DFD

DATA DICTIONARY

Data dictionary is also called with a system data dictionary is a catalog of facts and data information needs of an information system. In function to help system agent to interpreting application in detail and organization all of data element that utilized by system exactly so user and system analyst have same understanding basic about entry, output, storage and process. On analysis’s phase, data dictionary is utilized as communication device among system analyst with user. On system design phase, data dictionary is utilized to design input, reporting and database. Data flow on DFD has global character; the more detail information can be seen on data dictionary.

Data dictionary load things as follows:

· Name of data flow: must note that readers that require more explanation about a data flow can look for it squashy.

· Alias: alias or other name of data can written if available

· Data form: utilized to agglomerate data dictionary into its usage when designing of system

· Data flow: show that from where data flow and where data wend.

· Explanation: giving explanation about meaning of data flow

BALANCING IN DFD

· Data flow which it’s in and out from one process has to equal with data flow which it’s in and out from details of process on level under it.

· name of data flow which its in and out from one process must be same with the name of data flow which its in and out from details of that process

· Total and name of external entity of a process has to equal with total and name of external entity of details of that process

· Things that must be noticed on DFD who has more than one level:

o input and output balance must be available among one level and next level

o Balance among level 0 and level 1 is seen on input / output of data flow goes to or from terminal on level 0, meanwhile balance among level 1 and level 2 are seen on input / output of data flow goes to / from process that pertinent

o name of data flow, data storage and terminal on every level must be same if its object is same

PROHIBITION IN DFD

· Data flow may not from external entity directly to wend another external entity without passing a process.

· Data flow may not from data storage directly goes to external entity without passing a process

· Data flow may not of direct data storage wend to another data storage without passing a process

· Data flow from one process directly to wend another process without passing an data storage is advisable/can be avoided

DIAGRAM CASH INVESTMENT DATA

There are 2 forms of DFD:

1. Physical Data Flow Diagram (PDFD), more appropriately used to describe the existing system (old system). The emphasis is how the processes of the system is applied, including manual processes.

2. Logical Data Flow Diagram (LDFD), more appropriately used to describe the system that will be proposed (new system), with no emphasis on how the system implemented, but the emphasis only on the logic of the demand system, that is what the process logic needed by the system.

GUIDELINES TO DRAWING DFD

1. Identify the first unit outside of all involved in the system. For example, sales for the system have involved external entity such as customer, credit manager, warehouse division and delivery division.

2. Identification all of input and output that involved in union with the outside.

3. Draw the context diagram (context diagram) first. DFD is a tool for structured analysis. The structure of this system to try to describe the first time the outline (called by top level) and split them into the more detailed (called by lower level) is called overview diagram (level 0). Each overview will be drawn more detailed again called level 1, and each process in level 1 will be drawn back with a detailed level with a 2 and so on until each of these processes can not be drawn again.

4. Draw the hierarchy chart for all process that is in the system first. Tiered chart (hierarchy chart) used to prepare the DFD drawing to more levels down again.

5. Draw the sketch of DFD for overview diagram (level 0) based on process on the tiered chart.

6. Draw the DFD for next level which is level-1 and so on.

7. After all of level in DFD is drawn, next is draw the DFD for management reporting which its drawn separately.

8. after all of level in DFD is drawn, and then all of this DFD can combine in one diagram.

Reference:

ER Ngurah Agus Sanjaya. Slide Part 4 - DATA FLOW DIAGRAM.
HM, Jogiyanto. 2007. Analisis & Desain Sistem Informasi. Yogyakarta: ANDI.

Information Systems Analysis and Design [Part 3]

2009-03-28T02:02:00.001-07:00

EARLY OBSERVATION, ANALYSIS'S REQUIREMENT

CONCEPT OF INVESTIGATION SYSTEM

There is the difference distinctive among system's aim and condition of system actually. Reporting detects problem not quite a reality, that is:

- The target of system over ideal
- Lack for resource and or attitude
- System measurement less accurate
- The target of system which have under developed
- The difference among idle system and temporary system

Problem solving for the problems above are:

- System formulation that be walks or in other words is investigation in detail
- Getting ideal system consensus
- Develop severally alternative
- Choosing the best one alternative

The target of investigation is to show the problem that actually happens.

CONSTRAINT IN INVESTIGATION SYSTEM

When we do investigation, some constraints which often arise are about:

- Time
- Cost
- Science
- Politics
- Interference

RECOMMENDATION

Result of investigation is a recommendation which contain for example as follows:

- No action or problem undiscovered
- Doing system preserve or there are only a little problem
- Increasing user ability or skill
- Regarding system modification totally
- Placing happening problem into systems development plan which shortly be done

INVESTIGATION TACTICS

Why needs tactics in investigation system? Tactics needs in investigation system to find all problems, knowing cause of arise problem and determining solution in point. The tactics is done so all system element can accept solution offer without trouble their activity.

Severally tactics which can be done, that is:

- Listening system agent opinion
- Don't give startup resolving
- Comparing story some bodies system agent to same case
- Notice inconsistency logical problem

INVESTIGATION TECHNIQUES

Investigation techniques can do in two way which is directly and indirect. On directly we can use Questionnaires, Question-answer and Observation. Then on indirect we can use Procedural flow, Studying document, Sample and Tabular.

CURRENT SYSTEM DESCRIPTION

- Input
- Output
- File
- Data element
- Transactions volume and action document
- Data flow chart

ANALYSIS'S REQUIREMENT

Intensive interaction phase among system analyst with end user where systems developmental team point out its membership to get comment and user trust so gets good participation.

Four (4) goals that wants to be reached:

1. Explain comprehensive system
2. Figuring ideal information system
3. Taking in ideal information system to condition of currently by notices resource constraint
4. Giving push to wearing confidence into developmental system

Method that use in analysis's requirement are question-answer, Questionnaire, Observation, Analysis's procedure and Document observation.

RESOURCE CONSTRAINT

Resource constraint is influenced by:

~ Time
~ Money
~ Membership
~ Technology
~ External factor

Analysis's Requirement Document:

- Analysis's instruction: Relationship with end user, processes observation, about problem in data collecting

- User requirement: Real requirement, Report requirement, training requirement and new system influence

- System constraint: Explain the time and cost constraint, membership, technology and external factor

- Document as instrumental as data collecting, statistical consensus, logically and physical data flow, early data element in data dictionary

GENERATING SYSTEMS ALTERNATIVES

How to approach current system condition with condition of system which ideal?

- Making alternative to solve information system problem
- That best alternative applied by wisely

Strategy option:

o Distributed versus centralized processing
Changing information decision from centralized processing's data goes to decentralized end user responsibility center
o Integrated versus dispersed database
System designer shall regard data any kind incoming in database and one turns in at File
o Surround Strategy of System Development
Environmental surrounding of strategy is important in term confiscation because information system of other firm may in contrast to corporate currently.

Strategy option is done before operational scheme option

Operational scheme option

Scheme option can be agglomerated into:

>> Input
- - Online Vs Off Line Data Entry
- - Keyed Vs Machine Readable Data Entry
- - Centralized Vs Decentralized Data Entry
>> Processing
- - Batch Vs Realtime record update
- - Sequential Vs Direct Access to records
- - Single Vs Multiple User update of records
>> Output
- - Traditional Vs Turn Around Documents
- - Structured Vs Inquiry based reports

SELECTING THE PROPER SYSTEM

Strategy compares

Strategy compares is system compared based on cost and gain relatively; There is 3 A's system trick is said more superior with another system, if:

- A have inferior cost of B and both have same gain
- A have inferior cost of B and A produce gain more than B
- A and B have same cost but resulting gain of A is more

Severally System Compares Method:

1. Break Even point Analyisis
2. Payback Period
3. Discounted PayBack period
4. Internal Rate of Return

Cost category

- Hardware
- Software
- People
- Suppliers
- Telecommunications
- Physical sites

Cost detail

Comparing information system's cost through life system, analyst shall projection how much change of cost for the future and there is 3 models of information system's cost which is Linear, Exponential and Step Function.

Information system's cost can happen just once and also can happening chronically.

- information system's cost happening that just once which is on time's cost and development's cost that do happen while system development.
- Information system's cost happening continually among those is recuring's cost and operational cost where this cost happens while operating information system everyday.

INFORMATION SYSTEM FACTOR

Qualitative factor that aim good information system's performance among those:

- Reducing fault's level
- Reducing time to fix fault
- Reducing response time from workstation alternative
- Hastening time to supply information
- Increasing system security
- Increasing record's source update active
- Increasing user satisfaction

CORPORATE STRATEGY FACTOR

- Consumer satisfaction
- Sell level increases
- Consumer commitment and vendor
- Product marketing information

System learning presentation

>> Doing presentation in few words
>> Reducing technique's explanation in detail
>> presentation clearly with visual's assistive tool
>> If utilizes model to utilize assistive tool e.g. laptop so more informative
>> Emphasize gain of information system proposal with severally alternative that available appropriate condition which experienced by firm.

DECISION KEEP IT UP OR NOT

<> If firm decides to develop system therefore information department will do succeeding process which is Process System Design.
<> If contrariwise therefore System Development Life Cycle (SDLC) will be discontinued.
<> Oft will find problem with study's system and usually top management will ask for to do its reworking to study's system.
<> Model will explain some part step which to be repeated and sometimes information department will make decision to repeating steps before explain study's system.
<> With alternative, decision for repeating a SDLC's step in advance or not been called Go – No – Go Decision.

Information Systems Analysis and Design [Part-2]

2009-03-07T00:38:00.001-08:00

The importance of developing a system

System development can be interpreted to arrange a new system to replace the previous system as a whole or repair the existing system. The previous system need to be repaired because of a few things, which is:

a. Mark sense about problem that arises at previous system. The problems such as :

- Wrongness

Wrongness in previous system causes system that can't operate according to expected. An amiss can be as a fault that didn't intentional so cause truths of reducing data are secured.

- Organizational growth

Organization growth caused must be arranged a new system. The organization growth such as information requirement that progressively extends, data processing volume gets to increase, changing accounting principle a new one.

b. Get the opportunities

Information Technology expanding very quickly, then organizational start to feel that this TI require to be used ready to increase information. in emulation of market, speed of time efficiency or information very determining success or failure of plan which have been made arrangements for to reach for existing opportunities.

c. Existence of instructions (directives)
The arrangement of new system can be done because of existence of instructions from the leader or from outside of organization like regulation of government.

Purpose or goal of developing an information system

From the problems above, we can meet the purpose or goal of developing information system such as:

- to solving some problems

- reach for opportunity

- fulfilling given instruction

The organization's expectations after implementing an information system

As developing a new system, then will be happened the improvement in a new system. The improvement related to PIECES (is the acronym for easier), such as:

- Performance, the improvement of performance in a new system make the system will be effective. Performance can be measurement from throughput and response time where throughput is amount of work of which can done certain in a moment and response time is time mean which delay between two transactions.

- Information, the improvement of information quality which presented.

- Economy, the improvement of benefits and advantages or decreasing cost that happened.

- Control, the improvement of control to detection and repairing some faults and insincerity which possible happened.

- Efficiency, the improvement of operating efficiency. Efficiency related with how to use resource without doing extravagance.

- Services, the improvement of services given by system.

The principles of developing an information system

1. System for the management
2. System is big investment
a. Investigation of all alternative ( minimizing missing cost opportunity)
b. Best investigation have to be valuable : analysis cost-benefit & analysis cost-effectiveness

3. System need educated people
a Not educations have to be formal but can do on-the-job training.Activity steps and the tasks that must have to be done in system development. This activity is shown on System Development life cycle
4. System development processes not have to be successive.
5. Don't fear to cancel the project
6. System documentation for guidance in system development

Systems Development Life Cycle

The Systems Development Life Cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project from an initial feasibility study through maintenance of the completed application. Various SDLC methodologies have been developed to guide the processes involved including the waterfall model (the original SDLC method), iterative model and the spiral model.

Documentation is crucial regardless of the type of model chosen or devised for any application, and is usually done in parallel with the development process. Some methods work better for specific types of projects, but in the final analysis, the most important factor for the success of a project may be how closely particular plan was followed.

A. Waterfall model

The image below is the classic Waterfall model methodology, which is the first SDLC method and it describes the various phases involved in development.

Briefly on different Phases:

Requirement Analysis and Design

Analysis gathers the requirements for the system. This stage includes a detailed study of the business needs of the organization. Options for changing the business process may be considered. Design focuses on high level design like, what programs are needed and how are they going to interact, low-level design (how the individual programs are going to work), interface design (what are the interfaces going to look like) and data design (what data will be required). During these phases, the software's overall structure is defined. Analysis and Design are very crucial in the whole development cycle. Any glitch in the design phase could be very expensive to solve in the later stage of the software development. Much care is taken during this phase. The logical system of the product is developed in this phase.

Design

In system design functions and operations are described in detail, including screen layouts, business rules, process diagrams and other documentation. The output of this stage will describe the new system as a collection of modules or subsystems.

Implementation

In this phase the designs are translated into code. Computer programs are written using a conventional programming language or an application generator. Programming tools like Compilers, Interpreters and Debuggers are used to generate the code. Different high level programming languages like C, C++, Pascal and Java are used for coding. With respect to the type of application, the right programming language is chosen.

Testing

In this phase the system is tested. Normally programs are written as a series of individual modules, these subjects to separate and detailed test. The system is then tested as a whole. The separate modules are brought together and tested as a complete system. The system is tested to ensure that interfaces between modules work (integration testing), the system works on the intended platform and with the expected volume of data (volume testing) and that the system does what the user requires (acceptance/beta testing).

Maintenance

Inevitably the system will need maintenance. Software will definitely undergo change once it is delivered to the customer. There are many reasons for the change. Change could happen because of some unexpected input values into the system. In addition, the changes in the system could directly affect the software operations. The software should be developed to accommodate changes that could happen during the post implementation period.

B. Iterative model

In software development, iterative is used to describe a heuristic planning and development process where an application is developed in small sections called iterations. Each iteration is reviewed and critiqued by the software team and potential end-users; insights gained from the critique of iteration are used to determine the next step in development. Data models or sequence diagrams, which are often used to map out iterations, keep track of what has been tried, approved, or discarded, and eventually serve as a kind of blueprint for the final product.
The challenge in iterative development is to make sure all the iterations are compatible. As each new iteration is approved, developers may employ a technique known as backwards engineering, which is a systematic review and check procedure to make sure each new iteration is compatible with previous ones. The advantage of using iterative development is that the end-user is involved in the development process. Instead of waiting until the application is a final product, when it may not be possible to make changes easily, problems are identified and solved at each stage of development. Iterative development is sometimes called circular or evolutionary development.

C. Spiral model

The spiral model, also known as the spiral lifecycle model, is a systems development lifecycle (SDLC) model used in information technology (IT). This model of development combines the features of the prototyping model and the waterfall model. The spiral model is favored for large, expensive, and complicated projects.

The steps in the spiral model can be generalized as follows:

a. The new system requirements are defined in as much detail as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.

b. A preliminary design is created for the new system.

c. A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.

d. A second prototype is evolved by a fourfold procedure: (1) evaluating the first prototype in terms of its strengths, weaknesses, and risks; (2) defining the requirements of the second prototype; (3) planning and designing the second prototype; (4) constructing and testing the second prototype.

e. At the customer's option, the entire project can be aborted if the risk is deemed too great. Risk factors might involve development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer's judgment, result in a less-than-satisfactory final product.

f. The existing prototype is evaluated in the same manner as was the previous prototype, and, if necessary, another prototype is developed from it according to the fourfold procedure outlined above.

g. The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.

h. The final system is constructed, based on the refined prototype.

i. The final system is thoroughly evaluated and tested. Routine maintenance is carried out on a continuing basis to prevent large-scale failures and to minimize downtime.

Approaches of developing a system

There are several approaches to developing a system, that is:

>> Classical approach vs. structured approach

Classical approach is an approach of developing a system that follow steps at system life cycle without supplied with tools and techniques.
Troubleshoots which can arise from this approach, such as:

a. Difficult development.
Classic approach less give tools and techniques insides develop system and finally software development process becoming not directional and difficult to be done by programmer.
b. Treatment cost or system maintenance will be more expensive.
The expensive treatment cost at classic approach caused system documentation that developed less complete and less structured.
c. Possibility of big error.
This approach doesn't prepare to manner systems analysis to do system testing, so that system errors possibility will be bigger.
d. System achievement less well guaranteed.
Because classic approach less involve system user in system development, so system user needs are less matching with the one which desirable and as finally system that applied less success.
e. Applying system internal issue.
User will be startled and unaccustomed with new system suddenly introduced.

Structured approach equipped with tools and techniques that wanted in system development, so that the end result from system which developed be got system the structure will be defined well and clear.
In this approach, consumer involve from early to determine requirement of system and using tools like data of flow diagram

>> Piecemeal approach vs. system approach
Piecemeal approach is system approach development that emphasized at one particular activity or certain application. This approaching just notice target of activity or the application.
System approach is paying attention information system as one integrated unity for each activity or the application. This approach also emphasized in overall goal achievement from organization, not only in that information target.
>> Approach of bottom-up vs. approach of up-down
Bottom-Up Approach is beginning from level under organization, that is from formulation requirements to handle transaction and climb level on with formulate information need based on transaction. If Bottom-up approach is used in systems analysis steps, it also called by data analysis's terminology, because the becoming pressure is data who will be processed beforehand, information that will be yielded catch up to following the data.
Up-Down Approach on the contrary is beginning from level up organization that is from defining the target and organization policy. Step furthermore from this approach analyses requirement of information. After information is determined, then process goes to transaction processing, that is determination output, input, data base, operating procedure and control. When top-down approach used in systems analysis steps it is also called by decision analysis terminology, because the becoming pressure is information that wanted for making decision by management beforehand, then data which need to be processed will be defined to follow required information.
>>Total-system approach vs. modular approach
Total-system approach is the approach which developing a system together according to comprehensive. This approach less synchronized for complex system, because will be difficult be developed. This approach is feature classic approaches.
Modular Approach tries to divide complex system to simple some part, so that system easier will be understood and developed. Furthermore consequence system can be developed of time that planned, easy understood by system user and easy to maintain. This approach is feature structured approaches.
>> Great-loop approach vs. evolutionary approach
Great-loop approach applying change totally at a time use sophisticated technology. This change contains many risks, because computer technology so great-loop. This approach also too expensive, because need investment at the same moment for all technology that used and difficult to developed because it's too complex.
Evolutionary approach applies sophisticated technology just for applications that need that moment and will be developed for next periods based on technology development. This approach causes investment not too expensive and can follow fast technology development.

The meaning of methodology, method and algorithm

As we know there are approaches in developing a system. Now how to do these approaches? To developing a system, it is required by methodologies. Methodology are utilized methods, procedures, professions concept, rules and postulates that used by a science, art or the other. Method is someway systematic to work something. And algorithm is medley procedural to solve problems.

The classifications of development methodology

There are three classifications of developing a system, such as:

A. Functional decomposition methodologiesFunctional decomposition is emphasizing to divide a system becomes subsystem. There are the include in this group methodologies such as HIPO, Stepwise refinement, iterative stepwise refinement and information hiding.
B. Data-oriented methodologies
Data-oriented is emphasizing on processed data characteristic. This approach can be grouped in two:
a. Data-flow oriented: based on dividing system to modules pursuant to elements data types and logic behavior of these modules in system. There are the include in this group methodologies such as SADT (Structured Analysis and Design Techniques), Composite Design.
b. Data structure oriented: emphasizing structure of input and output in system. There are the include in this group methodologies such as JAD (Jackson's system development), W/O (Warnier/Orr).

C. Prescriptive methodology
This methodology usually has been provided by software maker factory. In this methodology including:
- - ISDOS (Information System Design and Optimization System)
- - PLEXSYS
- - PRIDE
- - SDM/70
- - SPECTRUM
- - SRES and SREM, etc.

Tools for developing a system

To do steps according with methodology developing a system, then needed a tools and techniques. The tools there are in the form of diagram and chart, such as : HIPO diagram, Data flow diagram, SADT, structure chart, Jackson's diagrams, etc.

Besides the tools that mention above, there are utilizes that used at all of methodology. The tools as a chart set that grouped by:

a. Activity charting: to figuring activity, example: chart's substituting, flowchart, etc.
b. Layout charting: to figuring layout
c. Personal relationship charting: to figuring person relationship, example: organization chart, working distribution chart

Techniques used in developing a system

Techniques used in developing a system, as follows:

a. Project management techniques, this techniques used to scheduling project, example: CPM and PERT
b. Fact finding techniques, techniques to gather and determines data / fact. The techniques that is:
- - Interview
- - Observation
- - Questionnaires
- - Sampling
c. Cost effectiveness analysis or cost-benefit analysis
d. Techniques for going meeting
e. Inspection techniques/walkthrough

The differences of being a system analyst and a programmer

System analyst is different with programmer, the differences are:

a. System analyst is people that studying problems and determine system user requirements to identify resolving, while programmer is people that writing program code bases engineering that made by analyst.
b. Responsibility a programmer is limited to computer program makings, but system analyst to system as a whole.
c. Knowledge a programmer is limited to computer technology, computer system, utilities and program language required. But system analyst must have a wide of knowledge.

The knowledge a system analyst should posses

System analyst must have a wide knowledge and skills. There are some skills which are very needed for a good system analyst.

1. Knowledge and skill about data processing technique, computer technology and computer programming

a. Technical skill that must have is including skill of using tool and technique for application software development.
b. Technical knowledge that must have knowledge about hardware, data communication technology, computer languages, operating system, utilities, and another.

2. Knowledge about business in general
This knowledge is wanted so that system analyst can communicate with system user.
3. Knowledge about quantitative method.
System analyst use many quantitative methods in build application models, like dynamic programming, regression, network, decision tree, trend, simulation and other as it.
4. Trouble-shooting skill.
System analyst must have ability to put complex troubleshoots that is faced by business, divide problem into parts, analyze it and then must can return composed to be a system can overcome troubleshoots.
5. Communication skill delivers staff.
System analyst must have ability to hold communication either through tongue or article.
6. Skills to builds relationship among personal
Human is factor critical insides system and human character one with another is different, so that need a skill to build connection or relationship among personal.

References:

Hartono, Jogiyanto.2005.Analisis dan Desain Sistem Informasi: Pendekatan Terstruktur, Teori dan Praktik Aplikasi Bisnis. Yogyakarta: Andi.

http://en.wikipedia.org/wiki/Software_development_methodology

http://searchsoftwarequality.techtarget.com/sDefinition/
0,,sid92_gci519105,00.html

http://searchsoftwarequality.techtarget.com/sDefinition/0,,sid92_gci519580,00.html

http://searchsoftwarequality.techtarget.com/sDefinition/
0,,sid92_gci755347,00.html

Umbrella (feat. Jay-Z)

2009-02-21T00:44:00.000-08:00

by Rihanna

Jay Z:

Ahuh, Ahuh (yea… Rihanna) Ahuh, Ahuh

Bm D
You had my heart, and we'll never be world apart

A G
Maybe in magazines, but you'll still be my star

Bm D
Baby cause in the dark, you can see shiny cars

A
And that's when you need me there

G
With you I'll always share

D
Because

G
Chorus: When the sun shines

D
We’ll shine together

A
Told you I'll be here forever

Bm
That I'll always be your friend

G
Took an oath Imma stick it out 'till the end

D
Now that it's raining more than ever

A
Know that we still have each other

Bm
You can stand under my umbrella

G
You can stand under my umbrella

D
(ella ella eh eh eh)

A
Under my umbrella

Bm
(ella ella eh eh eh)

G
Under my umbrella

D
(ella ella eh eh eh)

A
Under my umbrella

Bm
(ella ella eh eh eh eh eh eh)

Bm D
These fancy things will never come in between

A G
You're part of my entity, here for infinity

Bm
When the war has took its part

D
When the world has dealt its cards

A G
If the hand is hard, together we'll mend your heart

D
Because

Back to: Chorus

G
You can run into my arms

D
It's okay don't be alarmed come into me

(There's no distance in between our love)

G
So gonna let the rain pour

F#
I'll be all you need and more…

G
Because...

Back to: Chorus

G
It's raining (raining)

A
Ooo baby it's raining

F#
Baby come into me

Bm
Come into me

G
It's raining (raining) – FO/Fade Out

My FavouriTe Song!!!

2009-02-20T23:59:00.000-08:00

Brown Eyes

by Destiny's Child

Remember the first day when I saw your face

remember the first day when you smiled at me

you stepped to me and you said to me

I was the woman you dreamed about

remember the first day when you called my house

remember the first day when you took me out

we had butterflies although we tried to hide

and we both had a beautiful night

The way we held each others hand

the way we talked the way we laughed

it felt so good to find true love

I knew right then and there you were the one

I know that he loves me cause he told me so

I know that he loves me cause his feelings show

when he stares at me you know that he cares for me

you see how he is so deep in love

I know that he loves me cause its obvious

I know that he loves me cause it's me he trusts

and he's missing me if he's not kissing me

and when he looks at me his brown eyes tells his soul

Remember the first day, the first day we kissed

remember the first day we had an argument

we apologized and then we compromised

and we haven't argued since

remember the first day we stopped playing games

remember the first day you fell in love with me

it felt so good for you to say those words

cause I felt the same way too

The way we held each others hand

the way we talked the way we laughed

it felt so good to fall in love

and I knew right then and there you were the one

i'm so happy so happy that you're in my life

and baby now that you're a part of me

you showed me

showed me the meaning of true love

and i know he loves me

He looks at me and his brown eyes tell his soul

Information Systems Analysis and Design [Part I]

2009-02-19T22:37:00.001-08:00

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 characteristic system can be explained as a picture below:

CLASSIFICATION OF SYSTEM

a. Deterministic System

The certain system operate with behavior which have earned can be predicted, interaction between its shares can be detected categorically so that its output can be forecasted. For example: Computer program, executing precisely as according to its instruction network.

b. Probabilistic System

The System which is input and its process can be defined, but yielded output cannot be determined categorically. 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 is work automatically without existence of interfere in of external side of it.

e. Relatively Closed System

Is 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 boundaries.

f. Artificial System

The System is imitating occurrence in system. This system is formed pursuant to occurrence in nature where human being unable to do it.

g. Natural System

The natural system is occurrence in nature. For example: sea, solar system and others.

h. Manned System

The system is explanation of behavior 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.

WHAT IS INFORMATION?

Data is fact. Information is processing data into more useful things for the user who need it. If data is not useful to accept it so the data cannot be referred as by information.

In the information cycle, data that we input are processed in the database system. The output after data has been processed is information. So, user can use that to make a decision action. Result of the decision action is new data. New data comes for the input so information is being cycling again continuously.

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

Konsep Robot

2009-02-17T20:42:00.000-08:00

Banyak terdapat tanggapan mengenai konsep robot, dimana robot diandalkan sebagai tiruan manusia. Karena itu dicoba dibuat sebuah definisi untuk menghindari hal-hal yang tidak diinginkan. Definisi yang paling dapat diterima adalah dari “Robot Institute Of America”.

“Sebuah robot adalah sesuatu yang dapat di program dan diprogram ulang, dengan memiliki manipulator mekanik / pengerak yang didisain untuk memindahkan barang-barang, komponen-komponen atau alat-alat khusus dengan berbagai program yang fleksibel / mudah disesuaikan untuk melaksanakan berbagai macam tugas”

Dari definisi tersebut dapat dikatakan robot sebagai automasi yang dapat diprogram (Programmable Automation).
Sedangkan istilah Robotik Berdasarkan Webster adalah :

"Teknologi yang behubungan dengan mendesain, membuat, dan mengoperasikan robot."

Robotik ruang lingkupnya mencakup artificial intelegen, ilmu komputer, engineering mekanik, Psikologi, Anatomi, and bidang ilmu lainnya. Kata Robotik sendiri pertama kali digunakan oleh Issac Asimov pada tahun1942.

Headlines (Friendship Never Ends)

2009-02-15T22:58:00.000-08:00

oleh: Spice Girls

[Emma:]
The time is now or never to fit the missing piece
To take this song together,
You make me feel complete
We fall into the future,
And through the looking glass
The light shines over our heads and so it comes to pass

[Geri:]
To go beyond the surface,
To reach into your soul,
This love is not demanding,
My heart has told me so
I hold on to my hero with faith enough to find,
The power to imagine will keep this love alive

[Group:]
Lets make the headlines loud and true,
I wanna tell the world I'm givin it all to you
Lets make the headlines loud and clear
The best things suddenly happen when you are here
If i lost my way you'd carry me home
Take me all the way to heaven never leave me alone,
And its just like everything matters when you are near
(matters when you are near)

[Mel C:]
And it feels so good every bells gonna ring
Thsi love is alive and its making me sing
I could fly, wanna cry, want the whole world to know,
We are together, come on baby lets go

[Victoria:]
And words yet to be spoken
Will fall upon the page
Spelling out true devotion
Is all we need to say

[Group:]
Let's make the headlines, loud and true
(Say you love me and I'll say I love you too)
I wanna tell the world I'm giving it all to you
(Just remember what simple words can do)
Let's make the headlines, loud and clear
(All that I have I give to you my friend)
The best things suddenly happen when you are here
(Just remember friendship never ends)
And if I lost my way you'd carry me home
Take me all the way to heaven, never leave me alone (everything)
And it's just like everything matters when you are near (matters when you're near)
(Say you love me and I'll say I love you too)

Let's make the headline true this time
(Just remember what simple words can do)
There's no hiding from this magical state of mind
(I feel loved with you, I feel loved with you)
And if I lost my way you'd carry me home (I know, you take me,
all the way to heaven)
Take me all the way to heaven, never leave me alone (everything)
And it's just like everything matters when you are near (matters when you're near)
(Everything matters, it really matters)

[Mel B:]
'Cause I'm giving it all
Yeah I'm giving it all to you