Features: Why Study Electrical and Computer Engineering? Professor Timothy Chang Why Study Electrical and Computer Engineering? A Question and Answer Session with Professor Tim Chang How does electrical and computer engineering (ECE) differ from computer science? Which students should major in electrical and computer engineering? What do NJIT students enjoy most about their ECE major? What kind of high school students should consider majoring in electrical and computer engineering at NJIT? ECE is a major for students who like science and math as well as computers and electronics. How does computer engineering differ from computer science? What do your students most enjoy about ECE? Can you describe a hands-on project that your students are now working on? What are your classes like? In my classes, I use projects to motivate my students. What were your main interests when you were younger? What are your research interests? What kind of careers do ECE majors commonly pursue? (By Robert Florida, University Web Services)
Agile Software: Business Impact and Business Benefits - 10x Software Development Scrum Chickens and Pigs An interesting discussion came up on the Disciplined Agile Delivery discussion group on LinkedIn. Scott Ambler asked the question, "Is the chicken and pig analogy disrespectful?" The chicken and pig analogy is common in scrum. Posted on April 8, 2014 4:36:PM by Steve McConnell to 10x Software Development Estimation Types When I get asked for an estimate, my first response is not a cost, a date, or a functionality number. User Stories Ain't Requirements Ain't isn't really a word but people use it, so does that make it de facto a word? 2013 ECSE Discussion Topics Posted I host an executive discussion group in the Seattle area called the Executive Council for Software Excellence (ECSE). Software Project Archaeology New White Papers Now Available We've recently posted more new white papers on our website. Construx Executive Summit 2012
COBIT - IT Governance Framework - Information Assurance Control Looking for COBIT 5?COBIT 5 consolidates and integrates the COBIT 4.1, Val IT 2.0 and Risk IT frameworks and also draws significantly from the Business Model for Information Security (BMIS) and ITAF. Learn More Successful organizations understand the benefits of information technology (IT) and use this knowledge to drive their shareholders' value. Collaborate Join one of these COBIT 4.1-related communities and get in the conversation. COBIT—Use It Effectively COBIT Implementation COBIT 4.1 is an IT governance framework and supporting toolset that allows managers to bridge the gap between control requirements, technical issues and business risks. COBIT 4.1 Online COBIT's success as an increasingly internationally accepted set of guidance materials for IT governance has resulted in the creation of a growing family of publications and products designed to assist in the implementation of effective IT governance throughout an enterprise. Access COBIT 4.1 Online
What is Agile? Introduction and Characteristics. | Agile Advice - Working With Agile Methods (Scrum, XP, Lean) The word “Agile” refers to a type of method for getting work done. It’s all about doing valuable work with speed and quality. An Agile team delivers finished work frequently while working at a sustainable pace. Agile process consists of short iterations of work that deliver small increments of potentially shippable customer value. Frequent delivery ensures visibility of the work of the team, as well as its needs and obstacles, to all stakeholders. Agile refers to a discipline defined as the middle way of excellence between chaos and bureaucracy. Although Agile has emerged out of endemic crisis in the software development sector (but not exclusive to it!) Agile methods are made of processes, principles and tools. Although Agile cannot force people to be truthful, it reveals the direct consequences of opacity in an organization, confronts it and challenges it to change. Agile prioritizes by value, not “dependency”. Agile is the art of the possible. Please share!
BCS International Diploma in Business Analysis | Business analysis This Diploma is an international, industry-recognised certification that demonstrates the knowledge, skills and capabilities to be an effective business analyst. Who is this aimed at? Business and IT professionals who want to demonstrate they have a detailed understanding of business analysis best practice. What are the entry requirements? To proceed to the Diploma in Business Analysis you will need to have passed four modules: Practitioner Certificates in Business Analysis Practice Practitioner Certificate in Requirements EngineeringOne knowledge-based specialismOne practitioner specialism Please note that you will be examined on the latest version of the syllabus during the written and oral examination so you must ensure you are fully conversant with the latest version of the syllabus. What format is the exam? Up to 50 minutes oral examinationConducted by two examiners Discussion of experienceQuestions on topics from the syllabus, including the selected specialist modules What can I do next?
the decline and fall of agile It's odd to talk about the decline and fall of the agile movement, especially now that it's so popular, but I actually think the agile movement has been in decline for several years now. The State of the Art I've seen a shift in my business over the last few years. Now many people who call me already have Agile in place (they say), but they're struggling. Other consultants I've talked to report the same experience. The Role of Scrum Scrum is undeniably the winner of the agile method wars. But because Scrum works in short cycles and doesn't include any engineering practices, it's very easy for teams using Scrum to throw out design. What frustrates me the most is that this situation is entirely avoidable. Scrum, Misapplied It's not entirely Scrum's fault. Scrum includes these other points. Oh, and it also has a few mechanical things about a monthly Sprint and daily Scrum. You're Doing It Wrong There are a lot of teams right now failing with Agile. Failures in the Midst It's too bad.
Volere The Volere Requirements Specification Template has been downloaded in excess of 20,000 times. It has proved to be a valuable resource for organizations worldwide by saving significant time and money for their requirements activities. It does this by providing a rock-solid template and guide to writing appropriate requirements specifications. What follows is an extract of the full template, intended to give you enough information to familiarize yourself with it, and to provide an overview of the contents of the complete template, which runs to 90 pages. You can download the complete template upon payment of the usage fee. The fee includes the template (MS Word and PDF versions) and two worked examples of requirements specifications that use the template. Please note that when you click the "Buy Now" button, you will be redirected to Paypal to make your payment. Once your payment has been accepted, you will be redirected back to the download page on this Volere site. 1a. 2a. 3a. 3b. 4a.
Evidence Based Scheduling Evidence Based Scheduling by Joel Spolsky Friday, October 26, 2007 Software developers don’t really like to make schedules. Usually, they try to get away without one. “It’ll be done when it’s done!” Most of the schedules you do see are halfhearted attempts. Hilarious! You want to be spending your time on things that get the most bang for the buck. Why won’t developers make schedules? Over the last year or so at Fog Creek we’ve been developing a system that’s so easy even our grouchiest developers are willing to go along with it. The steeper the curve, the more confident you are that the ship date is real. Here’s how you do it. 1) Break ‘er down When I see a schedule measured in days, or even weeks, I know it’s not going to work. This forces you to actually figure out what you are going to do. If you are sloppy, and pick big three-week tasks (e.g., “Implement Ajax photo editor”), then you haven’t thought about what you are going to do. 2) Track elapsed time You can’t, really. Anyway. Summary
Coding Horror: What is "Modern Software Development"? Joel Spolsky came up with a twelve-item checklist in August, 2000 that provides a rough measure of-- in his words-- "how good a software team is": Do you use source control? Can you make a build in one step? Do you make daily builds? Steve McConnell enumerated Software's Ten Essentials in 1997, ten things that every software project should have: A product specificationA detailed user interface prototypeA realistic scheduleExplicit prioritiesActive risk managementA quality assurance planDetailed activity listsSoftware configuration managementSoftware architectureAn integration plan These are great lists. The lists are still highly relevant and definitely worth revisiting today. So here's my question to you: what core set of practices constitutes modern software development in 2006?
The Definitive List of Software Development Methodologies The nice thing about software development methodologies is that they are just like standards. There are so many to choose from! Come to think of it… some of them are standards (which more or less proves my point). Unfortunately, despite a lot of searching I haven’t found any page with a list of all major software development methods. So I decided to create one myself. Here it is… and I hope you will let me know what you think of it. Terminology In the various descriptions of methods on Wikipedia I have noticed many different terms being used, like method, process, model, framework, etc.. methodology (or method) – one specific collection of principles and/or practicesmethodology family – a set of alternative methods that exist alongside each otherframework – a skeleton (for methods) that must be customized/augmented before usemodel – a description (for methods) that must be implemented by a method, family or framework Methodology Leaders Get the book! Management 3.0 Methodology Followers
Coding Horror: Discipline Makes Strong Developers Scott Koon recently wrote about the importance of discipline as a developer trait: Every month a new programming language or methodology appears, followed by devotees singing its praises from every corner of the Internet. All promising increases in productivity and quality. But there is one quality that all successful developers possess. One trait that will make or break every project. Discipline. It's an interesting coincidence, because I recently gave a presentation to a group of developers on the topic of source control, and I found myself repeating that very same word throughout the presentation: discipline. Instead of a nice, structured set of projects with logical branches and tags, what ends up in source control is a hairy furball of crazily named folders with no logical structure at all. And it doesn't matter what language you use, either. So I'm inclined to agree with Scott. If you ladies leave my island, if you survive recruit training, you will be a weapon.