Book recommendation
-
Hi all, wasn't there a special forum for book recommendations? Anyway, what book(s) would you recommend when teaching beginners System Analysis and Design? I.e. the book should ideally both cover the analysis and design of the internals of an application (UML diagrams etc.), and also about UI design. Do you remember any books that fit the description? Also, if you remember any good articles online, that would also help a lot. Regards, Daníel
Wenn ist das Nunstück git und Slotermeyer? Ja! Beierhund das oder die Flipperwaldt gersput!
Book? What is this book thing you speak of? Is it a new type of website or blog or podcast? ;P
“If you want to build a ship, don't drum up people together to collect wood and don't assign them tasks and work, but rather teach them to long for the endless immensity of the sea” - Antoine de Saint-Exupery
-
Book? What is this book thing you speak of? Is it a new type of website or blog or podcast? ;P
“If you want to build a ship, don't drum up people together to collect wood and don't assign them tasks and work, but rather teach them to long for the endless immensity of the sea” - Antoine de Saint-Exupery
As Blank Reg put it in Max Headroom[^], "It's a non-volatile storage medium. It's very rare. You should 'ave one." Flynn
-
Hi all, wasn't there a special forum for book recommendations? Anyway, what book(s) would you recommend when teaching beginners System Analysis and Design? I.e. the book should ideally both cover the analysis and design of the internals of an application (UML diagrams etc.), and also about UI design. Do you remember any books that fit the description? Also, if you remember any good articles online, that would also help a lot. Regards, Daníel
Wenn ist das Nunstück git und Slotermeyer? Ja! Beierhund das oder die Flipperwaldt gersput!
One of my faves and one we used in Uni: Systems Analysis & Design in a Changing World, Fourth Edition by John W. Satzinger, Stephen D. Burd. Also covers OOAD, Interface Design, UML ..... and provides some good comparisons between Data Flow Diagramming and the Object-Oriented equivalents. Cheers Richard
-
Amar Chaudhary wrote:
Flowcharts
eek! OP was asking about OO concepts. Flowcharts belong to procedural processes. In UML, there are multiple dynamic diagrams that give better insight. Try activity diagram for looking at how use cases perform activities. Then there are state diagrams for the internal working of objects and interaction diagrams for the message flow.
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
Nagy Vilmos wrote:
Flowcharts belong to procedural processes.
You get a big "HWA???" for that one. A systems analysis is used for communicating information to more than just geeky devs. If you can't break the system processes down into diagrams (flowcharts, entity life histories, etc.) that can be read and confirmed by the customer and end users, then you ain't gonna make it as a SysAn. UML just doesn't cut it in the world outside the developers' cubicles.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Hi all, wasn't there a special forum for book recommendations? Anyway, what book(s) would you recommend when teaching beginners System Analysis and Design? I.e. the book should ideally both cover the analysis and design of the internals of an application (UML diagrams etc.), and also about UI design. Do you remember any books that fit the description? Also, if you remember any good articles online, that would also help a lot. Regards, Daníel
Wenn ist das Nunstück git und Slotermeyer? Ja! Beierhund das oder die Flipperwaldt gersput!
Hi As a student I worked through the following book: Systems Analysis And Design, Fifth Edition (Shelly Cashman) Book Summary: "Allow your students to do systems analysis and design right from the start This title presents students with real-world system analysis skills and techniques within the framework of the systems development life cycle (SDLC). Examples and cases are drawn from actual systems projects that enable students to learn in the context of solving problems, much like the ones they will encounter on the job. A blend of traditional development with an emphasis on the latest major software trends, outsourcing, application service providers, ERP, and more provide a well-rounded understanding of fundamental topics. Students will find concepts easy to understand through the clear writing style combined with figures that illustrate current technology and concepts." Regards, Rudolf
-
Hi all, wasn't there a special forum for book recommendations? Anyway, what book(s) would you recommend when teaching beginners System Analysis and Design? I.e. the book should ideally both cover the analysis and design of the internals of an application (UML diagrams etc.), and also about UI design. Do you remember any books that fit the description? Also, if you remember any good articles online, that would also help a lot. Regards, Daníel
Wenn ist das Nunstück git und Slotermeyer? Ja! Beierhund das oder die Flipperwaldt gersput!
Kendall and Kendall, Systems Analysis for overall and the Social science parts e.g. interviews and questionnaires.In its 3rd edition, I think. McFadden and Hoffer (can't recall the third author's name at the moment), Systems Analysis and Design. A good book in its 3rd or 4th edition.
Charles Wolfe C. Wolfe Software Engineering
-
Nagy Vilmos wrote:
Flowcharts belong to procedural processes
Don't know about you, but often find it help both me and the client if I produce a Flowchart of their business processes before I even start designing any computerised system to handle the process. Therefore flowcharts are still relivent as the Systems Analysis stage.
Steve Jowett ------------------------- Real Programmers don't need comments -- the code is obvious.
Steven J Jowett wrote:
but often find it help both me and the client if I produce a Flowchart of their business processes before I even start designing any computerised system to handle the process.
Completely agree. And let's not forget that even in OO, there are very often some procedures that need to be mapped out before they are mapped onto objects. Some might argue that a "Workflow" is a better fit, but what's a workflow but a fancy flowchart?
Currently reading: "A Desert Called Peace", by Tom Kratman
-
Hi all, wasn't there a special forum for book recommendations? Anyway, what book(s) would you recommend when teaching beginners System Analysis and Design? I.e. the book should ideally both cover the analysis and design of the internals of an application (UML diagrams etc.), and also about UI design. Do you remember any books that fit the description? Also, if you remember any good articles online, that would also help a lot. Regards, Daníel
Wenn ist das Nunstück git und Slotermeyer? Ja! Beierhund das oder die Flipperwaldt gersput!
Try these for Systems Analysis: Yeats, D., Wakefield, T., Systems Analysis and Design, Pearson Education Limited Laudon, K. & Laudon, J., Management Information systems, Pearson Education Inc. Avison, D., Fitzgerald, G., Information Systems Development, McGraw-Hill Publishing and this for User Interface design: Card, S., Moran, T., Newell, A., 1983, The Psychology of Human-Computer Interaction. Erlbaum, New Jersey Shneiderman, B. Plaisant, C. (2005) Designing the User Interface. Strategies for Effective Human-Computer Interaction (4th edn,) Pearson Education Inc. Nielson, J., Iterative User Interface Design [Online], Available: http://www.useit.com/papers/iterative\_design John, B., Keiras, D., 1996, Using GOMS for User Interface Design and Evaluation: Which Technique? [Online] Available: ftp://www.eecs.umich.edu/people/kieras/GOMS/Which-GOMS.pdf I could sell you a copy of the books if your interested.
Nobody can get the truth out of me because even I don't know what it is. I keep myself in a constant state of utter confusion. - Col. Flagg
-
Nagy Vilmos wrote:
Flowcharts belong to procedural processes.
You get a big "HWA???" for that one. A systems analysis is used for communicating information to more than just geeky devs. If you can't break the system processes down into diagrams (flowcharts, entity life histories, etc.) that can be read and confirmed by the customer and end users, then you ain't gonna make it as a SysAn. UML just doesn't cut it in the world outside the developers' cubicles.
I wanna be a eunuchs developer! Pass me a bread knife!
Mark Wallace wrote:
UML just doesn't cut it in the world outside the developers' cubicles
I totally disagree. UML is readable by all parties and especially in the case of use cases and activity diagrams, their simplicity makes them ideal for visualising concepts to non-technical types.
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
-
Hi all, wasn't there a special forum for book recommendations? Anyway, what book(s) would you recommend when teaching beginners System Analysis and Design? I.e. the book should ideally both cover the analysis and design of the internals of an application (UML diagrams etc.), and also about UI design. Do you remember any books that fit the description? Also, if you remember any good articles online, that would also help a lot. Regards, Daníel
Wenn ist das Nunstück git und Slotermeyer? Ja! Beierhund das oder die Flipperwaldt gersput!