UML diagrams

What is UML 

         UML diagrams are draws to help you visualize your project structure. its used to communicate a software design among team members, 

so its easy to understand how system conponents  interact in a drawings and diagrams; rather than reading someone code. 

Most of UML diagrams are high-level representation of code, and not concerned with implementation details.

Best way to use UML, is up to you

You can use UML in two different ways, as forward engineering or reverse engineering 

• Forward engineering, when you draw your system UML diagrams before coding, this is called forward engineering. as you will follow your UML design in the coding phase
• Reverse engineering, when you have a code, and to translate it to UML diagrams for easy understanding and communication with the team members. here you do the process in reverse order

How people use UML

             In software community, people use UML with different perspective, there are three main perspectives on how to use UML

• Sketch
• you do informal sketches, that depict the whole system, and omit details, this is the common method
• Blueprint
• you dig into more details of the design, in this methods, its handled to software deigner who will convert the system concept into easy small components in UML diagram that developers can follow. software designer may be a more experienced developers or a specialized one in software design. 
•  The difference between sketchy and blueprint UML diagrams is blurry. and could go between those perspective. so its not easy to look at UML diagram and say "this is a sketch diagram" or "i am sure this is a blueprint diagram". 
• Programming language
• not a common method of using UML, where it use UML as programming language. and it has its own UML compiler. however this approach is not practical most of the time

Some of common UML diagrams

• class diagram
• sequence diagram
• use cases
• state diagram
• activity diagram (or flow chart)

and we have uncommon as well

• communication diagram
• packages diagram
• timing diagram

So that's it for UML, in the coming posts i will dig into more details of common UML diagrams, and show some snapshots of "Day Player app" UML diagrams to see the UML concepts in actions.

Salam,

M.Aleem

Day Player Icon evolution

 You will see the app icon life cycle. its all about iteration, and find something to improve from time to time.  

App icon is more important than it's name.

What icon represent, and why its so important.  

Icons is your business cards, when some one in the Appstore search for specific application by keywords, your icons stand shoulder to shoulder to other icons. 

Day player, early wire-frames, take a peek

In the last post on the Wire-frames and prototype, we talked about what is Wire-frames  and what is the goal of this process,

in this post i will share with you the initial app Wire-frames to get idea of the whole app navigation system, and to take a peek on what you would expect in the next days. 

Wireframing and Prototype

What is wireframe

Wireframe is a part of the interface design process,  where you ignore any aesthetic related processes. that mean you are concerned with the layout of objects, rather than the color and shape of these objects,

so you can use it like a map or story board of your application session

 

Day player architecture

  

Are you serious, its just a time management app !!!! 

Architecture (or High-level) design, shaping your project path

what is software architecture.

after you defined your problem and get the right requirements, you need an overview of the whole system, so you want to define the main components and how they relate to each other.