Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Software Engineers - how do you work with the Systems Engineers? (Book recommendation?)

Software Engineers - how do you work with the Systems Engineers? (Book recommendation?)

Scheduled Pinned Locked Moved The Lounge
algorithmsbusinessquestiondesignhardware
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    AmazingMo
    wrote on last edited by
    #1

    Hello World, I work for a business that develops devices that incorporate embedded software. In the past, these devices (no, I won't say what they are), have been pretty simple, but with increasing competition and customer expectations they are getting increasingly complex. What we used to do was put the "software" requirements into our system spec so that validation of that design would happen during system test, (which was not so unreasonable back in ye olde days of simple requirements). The problem is that the system engineers are now struggling with the complexity. What we want to do is redefine the process so that the system spec (and required system level testing) are framed in terms of lower level components, such that the system spec is smaller and more comprehensible. My question is whether there is a good software engineering book out there that deals with the system level questions, is comprehensible, and is NOT targetted at military/safety critical systems. We release a new product approximately every 6 months, so the process can't be too heavyweight. I have been searching Amazon, etc, but am swamped by the variety of texts, so some direction is very welcome. Thanks, P.

    M 1 Reply Last reply
    0
    • A AmazingMo

      Hello World, I work for a business that develops devices that incorporate embedded software. In the past, these devices (no, I won't say what they are), have been pretty simple, but with increasing competition and customer expectations they are getting increasingly complex. What we used to do was put the "software" requirements into our system spec so that validation of that design would happen during system test, (which was not so unreasonable back in ye olde days of simple requirements). The problem is that the system engineers are now struggling with the complexity. What we want to do is redefine the process so that the system spec (and required system level testing) are framed in terms of lower level components, such that the system spec is smaller and more comprehensible. My question is whether there is a good software engineering book out there that deals with the system level questions, is comprehensible, and is NOT targetted at military/safety critical systems. We release a new product approximately every 6 months, so the process can't be too heavyweight. I have been searching Amazon, etc, but am swamped by the variety of texts, so some direction is very welcome. Thanks, P.

      M Offline
      M Offline
      Marc Clifton
      wrote on last edited by
      #2

      AmazingMo wrote:

      What we want to do is redefine the process so that the system spec (and required system level testing) are framed in terms of lower level components, such that the system spec is smaller and more comprehensible.

      What you are describing sounds like it could benefit from UML, because with UML, you can work with designs at the 30,000 foot level and then drill down into them to describe (and discover!) the component "graph", if you will. I've found it to be very helpful for that. So maybe what you really need is a process and a tool that supports that process, rather than a book. ;) Marc

      Thyme In The Country Interacx My Blog

      A 1 Reply Last reply
      0
      • M Marc Clifton

        AmazingMo wrote:

        What we want to do is redefine the process so that the system spec (and required system level testing) are framed in terms of lower level components, such that the system spec is smaller and more comprehensible.

        What you are describing sounds like it could benefit from UML, because with UML, you can work with designs at the 30,000 foot level and then drill down into them to describe (and discover!) the component "graph", if you will. I've found it to be very helpful for that. So maybe what you really need is a process and a tool that supports that process, rather than a book. ;) Marc

        Thyme In The Country Interacx My Blog

        A Offline
        A Offline
        AmazingMo
        wrote on last edited by
        #3

        Marc Clifton wrote:

        what you really need is a process

        Yes, that's right. I'm looking for books that advocate a process, and give a rationale/justification for the process. Thanks for commenting. P.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups