Composing Software Architecture Document
| April 3rd, 2008I work as software engineer in an australian company that headquartered in Bali. A couple weeks ago, I was assigned to an internal project. The project manager asked me to develop the Software Architecture Document. Since I am still junior, I got no idea in making the SAD. Where should I should start was someting I wonder. All the team members are also junior. So I decided to ask to my senior worked in another project. Here’s the conclusion how to create the SAD.
1. See the Software Requirements Specification document as the starting point. The use case diagram in that document is actually the starting point.
2. After that we are then ready to create the Entity Relationship Diagram as well as the sequence diagrams. But, we need to detail the use case first so that we know what is needed in the database and how the processes flow.
3. And the objects and the message calls in sequence diagrams can be used to create the class diagram. Do not forget to define the dependencies between classes.
Actually not that easy in creating the SAD, but I hope that can help to create the SAD for the beginner such me
Do you remember my YM status when we were at the course? SAD makes life better!!! wkwkwkwkw…
wkk…
Yaps SAD makes my life better too…
wkk..
halah apanya sih yang susah dari SAD lha wong kamu aja masih bisa posting buat blog lu aja
wkkkk cih . . .
wkkkk
pisss
@Agung: wkk…
Buset…Posting ini nyolong2 gung :p
Kalo lo yang buat SAD sih, kecil!!
Wong pengalamannya uda di Newmont :p
wkk
kalo gw yang ngerjain tu kacau wkkk :
ERD kaga ada PK n relasi -> biar gampang querinya
Class Diagram kaga usah dikasih -> biar jadi prosedural aja
wkkkkk maklum gw kan masih kacrut wkkkk
@Agung: Yeah it’s hard at first to reach object-oriented design, but it’ll become easy at maintenance
SAD? zzz…zzz…zzzzzz….
Ntar klo dah canggih ajarin gw y lus..
your space is amazing!
I will come into your blog spaces at the first time you update.