23 Juni 2020 Keresahan seorang anak, istri, adik dan Ibu.

23 Juni 2020

Gak tau kenapa tetiba keikiran sesuatu yang mengganggu. Entah ini hanya pikiran saja atau emang sudah ada dan merasa tertekan dan akhirnya keluar dipikiran dan menjadi sesak di dada. Saya mohon jangan judge kami seperti apa yang kalian lihat. kalian gak tahu dalam diri kami seperti itu. kami harus mengalah sama ego kami, cukup kalian diam saja dan jangan berbicara yang tidak tahu apa-apa. kami berdua hanya berusaha untuk adil itu saja. belum cukup kah kami berada disini lebih lama. kami tahu untuk sesama makhluk hidup apalagi yang memiliki hubugan yang erat harus saling membantu. kami paham betul dengan seperti itu tapi kalau ada permainan dibelakangnya yang kami tidak tahu atau tidak adanya transparansi kami tidak suka. kami akan merasa sedih saja apa ini yang dikatakan keluarga seperti yang kamu dan yang lain bilang. kami selalu mencoba membantu apabila ada yang membutuhkan bantuan kami tapi kalau seperti ini kami tidak begitu suka. saya paham yang dinginkan oleh orang tua apalagi itu seorang ibu agar semuanya baik-baik saja. tapi maaf ibu kami juga punya prioritas kami masing-masing. saya harap masalah ini bisa terselesaikan tanpa adanya rasa dengki dan dendam. kami mohon percayalah pada kami, kami bisa menyelesaikan ini dengan bergotongroyong bersama. kami doakan kehidupan kalian juga akan membaik.

Kabar Abid Sakit

02 September 2019

Ini hari lahir aku, tapi jadi hari dimana aku harus mendapatkan kabar anak yg aku cintai yang aku sayangi mengalami hal yang bikin aku merasa gagal menjadi seorang ibu. sesungguhnya apapun akan aku korbankan hingga nyawa pun akan aku korbankan untuknya harus merasakan penyakit menyebalkan itu. Abid dinyatakan positif terpapar penyakit ini. dalam hati seorang ibu banyak sekali cambukan seperti joroknya kamu, egoisnya kamu sering ajak anak keluar rumah malam-malam, dll.
kalau aku boleh pilih biar aku aja yang harus minum obat tiap hari, atau aku cegah semuanya dari awal. tapi aku juga bingung ini penyakit bisa datang dari ap dan siapa.

06 November 2019


Abid kembali ke rumah sakit mukanya pucat pasi tidak seperti sedia kala, "Ya Allah apalagi ini, apa yang terjadi pada buah hati Hamba.". Ngiris rasanya lihat tangannya membiru setiap selesai ambil darah. dari hasil darah pun belum ketemu hasilnya apa. sampai ahirnya abid harus masuk ke rumah sakit kembali dan menginap selama 1 minggu. akhirnya ketahuan bahwa hatinya tdak kuat dengan obat yang ia konsumsi tiap hari. Cambukan kesekian kalinya pada diri ini jad selama ini yang aku kasih itu penyebab dia semakin buruk. Ya Allah maafkan hamba yang maish belum bisa yang terbaik untuk titipan Mu. hari demi hari kondisinya membaik akhirnya obat diganti menjadi lebih cair. tetap aku merasa menjadi ibu yang tidak berguna untuk anak aku sendiri.


12 Maret 2020


Pemeriksaan terakhir untuk penyakitnya, setelah daftar abid diminta untuk di rontgen kembali.

Pengalaman Lahiran Abid '31 Desember 2018'

31 Desember 2018

Ini adalah hari dimana kebahagiaan dalam hidupku hadir, menjadi wanita seutuhnya, menjadi ibu yang harus selalu sabar dengan semua keadaan..

Class Diagram Blog

           Hi friends, what are you doing?? I attended last week about my business and learn elektrolis class diagram in astah. My lecturer told me to make a class diagram of the blogs that have been created. I have confused this class diagram. After a week I meditate I have finally found an idea that I created a class diagram blog below like appearance.

 

          You know it's not about class diagram? Do not know well, okay we'll learn a little about the class diagram. In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among objects.

              

              The class diagram is the main building block of object oriented modelling. It is used both for general conceptual modelling of the systematics of the application, and for detailed modelling translating the models into programming code. Class diagrams can also be used for data modeling. The classes in a class diagram represent both the main objects, interactions in the application and the classes to be programmed. A class with three sections.

            In the diagram, classes are represented with boxes which contain three parts:

• The top part contains the name of the class
• The middle part contains the attributes of the class
• The bottom part gives the methods or operations the class can take or undertake

          In the design of a system, a number of classes are identified and grouped together in a class diagram which helps to determine the static relations between those objects. With detailed modelling, the classes of the conceptual design are often split into a number of subclasses. In order to further describe the behaviour of systems, these class diagrams can be complemented by state diagram or UML state machine

            

             To specify the visibility of a class member (i.e., any attribute or method) these are the following notations that must be placed before the member's name:[3][citation needed]

"+"       Public

"-"       Private

"#"       Protected

"/"       Derived (can be combined with one of the others)

"_"       Static

"~"       Package

               A relationship is a general term covering the specific types of logical connections found on class and object diagrams. UML shows the following relationships:

              An association represents a family of links. Binary associations (with two ends) are normally represented as a line. An association can be named, and the ends of an association can be adorned with role names, ownership indicators, multiplicity, visibility, and other properties.
There are four different types of association: bi-directional, uni-directional, Aggregation (includes Composition aggregation) and Reflexive. Bi-directional and uni-directional associations are the most common ones.
                For instance, a flight class is associated with a plane class bi-directionally. Association represents the static relationship shared among the objects of two classes. Example: "department offers courses", is an association relation.

Aggregation

                 Aggregation is a variant of the "has a" association relationship; aggregation is more specific than association. It is an association that represents a part-whole or part-of relationship. As a type of association, an aggregation can be named and have the same adornments that an association can. However, an aggregation may not involve more than two classes.

               Aggregation can occur when a class is a collection or container of other classes, but where the contained classes do not have a strong life cycle dependency on the container—essentially, if the container is destroyed, its contents are not.

                In UML, it is graphically represented as a hollow diamond shape on the containing class end of the tree with a single line that connects the contained class to the containing class. The aggregate is semantically an extended object that is treated as a unit in many operations, although physically it is made of several lesser objects.

Composition

                 Class diagram showing Composition between two classes at top and Aggregation between two classes at bottom. Composition is a stronger variant of the "owns a" association relationship; composition is more specific than aggregation.

                 Composition usually has a strong life cycle dependency between instances of the container class and instances of the contained class(es): If the container is destroyed, normally every instance that it contains is destroyed as well. (Note that, where allowed, a part can be removed from a composite before the composite is deleted, and thus not be deleted as part of the composite.)


               The UML graphical representation of a composition relationship is a filled diamond shape on the containing class end of the tree of lines that connect contained class(es) to the containing class.
Differences between composition and aggregation

                When attempting to represent real-world whole-part relationships, e.g., an engine is a part of a car, the composition relationship is most appropriate. However, when representing a software or database relationship, e.g., car model engine ENG01 is part of a car model CM01, an aggregation relationship is best, as the engine, ENG01 may be also part of a different car model. Thus the aggregation relationship is often called "catalog" containment to distinguish it from composition's "physical" containment.

                The whole of a composition must have a multiplicity of 0..1 or 1, indicating that a part must belong to only one whole; the part may have any multiplicity. For example, consider University and Department classes. A department belongs to only one university, so University has multiplicity 1 in the relationship. A university can (and will likely) have multiple departments, so Department has multiplicity.

Class level relationships
Generalization 

Class diagram showing generalization between one superclass and two subclasses

           The Generalization relationship ("is a") indicates that one of the two related classes (the subclass) is considered to be a specialized form of the other (the super type) and superclass is considered as 'Generalization' of subclass. In practice, this means that any instance of the subtype is also an instance of the superclass. An exemplary tree of generalizations of this form is found in binomial nomenclature: human beings are a subclass of simian, which are a subclass of mammal, and so on. The relationship is most easily understood by the phrase 'an A is a B' (a human is a mammal, a mammal is an animal).

            The UML graphical representation of a Generalization is a hollow triangle shape on the superclass end of the line (or tree of lines) that connects it to one or more subtypes.

                  The generalization relationship is also known as the inheritance or "is a" relationship.

                 The superclass (base class) in the generalization relationship is also known as the "parent", superclass, base class, or base type.

               The subtype in the specialization relationship is also known as the "child", subclass, derived class, derived type, inheriting class, or inheriting type.

             Note that this relationship bears no resemblance to the biological parent/child relationship: the use of these terms is extremely common, but can be misleading.

•     Generalization-Specialization relationship

                A is a type of B

               E. g. "an oak is a type of tree", "an automobile is a type of vehicle"

                 Generalization can only be shown on class diagrams and on Use case diagrams.

Realization

                In UML modelling, a realization relationship is a relationship between two model elements, in which one model element (the client) realizes (implements or executes) the behavior that the other model element (the supplier) specifies.

             The UML graphical representation of a Realization is a hollow triangle shape on the interface end of the dashed line (or tree of lines) that connects it to one or more implementers. A plain arrow head is used on the interface end of the dashed line that connects it to its users. In component diagrams, the ball-and-socket graphic convention is used (implementors expose a ball or lollipop, while users show a socket).

       A realization is a relationship between classes, interfaces, components, and packages that connects a client element with a supplier element. A realization relationship between classes and interfaces and between components and interfaces shows that the class realizes the operations offered by the interface.
General relationship
Class diagram showing dependency between "Car" class and "Wheel" class (An even clearer example would be "Car depends on Wheel", because Car already aggregates (and not just uses) Wheel)
Dependency

          Dependency is a weaker form of relationship which indicates that one class depends on another because it uses it at some point in time. One class depends on another if the independent class is a parameter variable or local variable of a method of the dependent class. This is different from an association, where an attribute of the dependent class is an instance of the independent class.
Multiplicity

       The association relationship indicates that (at least) one of the two related classes makes reference to the other. In contrast with the generalization relationship, this is most easily understood through the phrase 'A has a B' (a mother cat has kittens, kittens have a mother cat).

             The UML representation of an association is a line with an optional arrowhead indicating the role of the object(s) in the relationship, and an optional notation at each end indicating the multiplicity of instances of that entity (the number of objects that participate in the association).

Use Case Blog

Hello, How are you today?? hi meets again with me... This time, I wants to explain about use case... Use case already Dian makes while lecturing carry on business elektrolis yesterday's week...  Previously have available one knows haven't hit Use Case that what?? Haven't?? Are you really dont kown anything about Use Case?? Okay, I will explain about Use Case that what? and its utility for what??  

 Use Case Blog's Image

A use case analysis is the most common technique used to identify the requirements of a system (normally associated with software/process design) and the information used to both define processes used and classes (which are a collection of actors and processes) which will be used both in the use case diagram and the overall use case in the development or redesign of a software system or program. The use case analysis is the foundation upon which the system will be built.

Use case is diagram figures fungsionalitas that expected of one system. One that is emphasized is “ what ” one be built by system, and is not “ how ”. One use case explain one interaction among actor with system. Use case constitutes one given work,logs in to system, create one shopping list. A actor is one entitas man or machine that gets interaction with system to do particular works. (Wahono, R. S,  2003) .

Use case is diagram can really help if we are arranging requirement one system, comunication is design with client, and designs case's test for all feature whatever available on system. One use case can included by more than one use case any other, so duplication fungsionalitas can be avoided by draws out fungsionalitas that common. 

One use case that extend use case can also any other with behaviour its own. While generalizing relationship among use case points out that use case the one constitutes specialization of another one.

• Actor: system user / something that gets interaction with explain system orders, are not wearing individual.  
• Use case: purposes specific trick system by actor. 
• < <include>  , which is deportment which shall be accomplished that one event can happen, where on this condition one use case is part of use case another.  
• < <extends>> , deportment that just walking under condition of particular as moves alarm. 
• Generalization, called also inheritance (endowment), one element gets to constitute specialization of another element. 
• Association, linking link among element.  

Use case manage profile's image

Now you have known that Use Case's cannikin what.. After knows Use Case that what now I will word about use case already I make week yesterday..  Yesterday I have made usecase about blog this.. First from User 1 and User 2 both all the same personations myself that gets to do everything to blog this.. This here, User can do manage profile user its own..

While is manage profile, user can entry profile new, update profile so long and delete profile. Entry our profile just fills in form already being provided by blog that. If inlay fault happening profile we can click switch edit profile on blog. And if wants to remove many profile that doesn't want post to public on blog, we just get to edit profile then erases profile wants obliterate then we can click switch save. That is explan to manage profile blog.

               

use case manage article's image

User can also manage posting article that wants post to public. While is manage article, user can entry new article, update long time article, and delete article already we post before. Entry article first we click new post, blog will provide sheet of paper for our place write that article. We can choose writing type, writing measure and writing color. After at writes its article then click knobbed save or post. If we want to edit already we post in advance we just double click that article then switch click edits then typing what do want to be editted then switch click save or post. If we want to delete article already we post in advance we just double click that article, then rights click to choose delete. 

                Besides entry new article, update long time article, and delete article already we post before. We can also entry comment, update comment and delete comment on article. One that sees our blog even gets entry comment, update comment and delete comment. While entry comment we just write komen at form already being provided by blog.

 

use case manage template's image

Besides gets manage article and manage profile we that manage template can also what do want we use. We can entry new template, update so long template or delete even existing template. While entry template new we get to click switch template you can choose template already been provided. Or wants to own make you just click edit HTML template is entry after that code tempalte already looks for at Google after that clicks save. If wants update or delete tempalte you do step as upon.

use case manage layout's image

             We that manage layout blog can also what do we make. Menage layout blog just can get to edit layout. By layout click then its position move given up by we are click afterwards save.

use case login's image

                 While is we manage all that we that log in shall beforehand. Log in shall can accord password and username. So we shall log in before can just do that above.  

use case appl for google adsense’s image