Systems Analysis and Design Methods

by Whitten

Allows students to practice systems analysis and design, not just read about it. New chapters on Use Cases, Object-Oriented Analysis, and Object-Oriented Design allow the instructor to choose the ballance between structured and object-oriented methods.

Genres: Nonfiction, Business, Library Science, Programming, Reference, Textbooks, Science

780 pages, Paperback

First published January 1, 1000

Reviews

[owleeya · Rating 3 out of 5]

Demi mengejar Goodreads challenge, buku yang dibaca agar bisa lulus kuliah pun jadi.

/heh

Sedikit cerita, jadi buku ini dipake saat semester 6, tapi mata kuliahnya gak jelas, tiap pertemuan dipake buat presentasi dari hasil nerjemahin buku ini per bab.

Saya lulus matkulnya sih, ya lumayan lah dapet nilai B juga....

...tapi saya gak tau sebenernya output dari kuliah tersebut apaan sih?

Saya kebagian nerjemahin yang bab-bab awal, tentang building block sistem informasi, terus ke sananya gak mudeng karena gak pernah merhatiin temen-temen saya saat presentasi.

Ternyata oh ternyataa buku ini lah yang dikasih sama dosen pembimbing saya saat saya ambil TA di semester 8. Dan sedikit nyesel kenapa waktu saat semester 6 kemarin itu gak dibaca dengan sungguh-sungguh ini buku, kan lumayan bisa dapet A, 3 sks lagi...

Ya udahlah lumayan nambah-nambahin buku buat challenge~

[Christopher · Rating 3 out of 5]

As with some other posts on this shelf, I have not read the entire volume. In this case, only selected chapters were included in the special edition made for the Drexel class.

This was a much more technical, and therefore challenging and interesting, book than the Experiencing MIS text for the first half of class. Again, the authors know they are writing a textbook and address the students as such. Again, the target student bady does not match with the cadre in an MLIS class - this text is aimed at students expected to become system analysts and go on to serve in IT departments at various businesses, not the proto-librarians I'm in class with. Because of this, the text occasionally assumes a level of programming knowledge that I didn't have (nor did any of my class-mates). But the authors didn't depend on that knowledge, instead trying hard to downplay the role of programmeds and application developers in favor business process analysis and revision.

There is something very strange about how much of business process management has been effectively ceded to technology divisions in modern corporations. An organization doesn't need to have computers to have a need for clear and consistant procedures. A database does not need to be electronic either - you'd think the librarians and records managers of the world would know this having created so many of the filing systems and search logics that allows computers to be invented in the first place

[James Fearn]

Have electronic version too

[愛苦虚 · Rating 3 out of 5]

Looking at this as a relic of the mid-2000s, designed to prepare "information services" people to work on "enterprise software" for large corporations, it is a historical account from an era when a server was a metal box in the other room, devs did no ops, and "the cloud" was just rising over the horizon. Within the verbose and jargon-heavy definitions there are some generally salient truths. It lacks technical depth and is not a particularly entertaining read, but there are some interesting thought exercises presented. I paid money for a "live" college class where the lectures and final exam were entirely based on content from this textbook's supporting website and our assignments on system infrastructure design hadn't been modified since 2007, but at least I didn't have to buy this thing.

[Kartika · Rating 5 out of 5]

mau kerjain tugas

[Elizabeth · Rating 4 out of 5]

Borrowed from the Kresge professional development collection and skimmed for useful content for LIS490TEL's week on systems analysis and design. My impression is that this is intended to be a textbook for BBA/MBA students, and while I can't pass judgement on its efficacy for that purpose, it certainly provided more than enough depth and breadth of content to apply to my little class.

I'm hoping that coming at this content from a business perspective - rather than the often extremely messy framework of libraries - will be useful for my students; it certainly has been for my own purposes. By that I mean - libraries and librarians often have a difficult time balancing their service orientation with the (financial, economic, cost/benefit) bottom line. My impression from my three libraries' worth of experience is that most librarians could benefit from a course - or at least a workshop - in the content covered in this book.

[Christina Maya · Rating 5 out of 5]

uhmm, my friend, Febri, just brought that to office. And since Feb 2007, i just read 10 pages of all..
Nice try for me! =D

[Mike Daigle · Rating 3 out of 5]

I learned that I know way too little about systems analysis and design methods. Ugh!

[Mia · Rating 1 out of 5]

I had to read this for school and I read the whole thing so I'm counting it on my list of what I read for the year. But I do not recommend it.

[Eric · Rating 3 out of 5]

Advice to college students: Buy this Indian Edition and save hundreds on the cover price. Very technically boring stuff here.

[Bushra GM · Rating 3 out of 5]

I think this is The Book , Great one :) a lot of Methodolgies and Methods to design your Projects

[Peterwilliam]

grad school textbook - no rating/review

[Terri Jones · Rating 5 out of 5]

Fundamentals of Business Systems Development course at University of Phoenix.

[Izar]

apa ni sudana

[Jaypee Soniel · Rating 4 out of 5]

f

[Soumya Biradar]

nice book

[Talbert Houle · Rating 3 out of 5]

Read this book for a Master's Degree course.

[Eugenio Puente Perazzo · Rating 5 out of 5]

Good book

[Ainul]

gg

[Sandeep]

hhisjdljaldklajdhjkalildsjlakjsljalk

[Cahit · Rating 5 out of 5]

Includes lots of methodologies and methods to design your projects.